I’m trying to make Sculpt OS my daily driver and looking into a way of deploying different “preconnected” components.
I’ve already figured out that out-of-the box Sculpt OS has launchers and presets:
While latter presets are a different /config/deploy file variations that are loaded from scratch deployed with the System button under Presets tab/button in Leitzentrale and located in /config/presets/.
The former are components configurations that are added to the running system, deployed via + button under Options tab/button in Leitzentrale and located in config/launchers/.
So if I want to have a Falkon browser with specific connections that I want to start and stop at will without manually “connecting” it every time I need to create a specific launcher for it inside /config/launchers/. Essentially to copy-paste a part of the deploy into a launcher file and tweak it a bit.
The only issue with this is that /config lives only in memory while system is running and gets recreated from scratch on reboot.
I tried to just copy a launcher to the used fs under the same path /config/launchers/- it didn’t work.
How I can keep my launchers from disappearing after reboot?
The default launchers provide some components that I deploy always and essentially they become part of the deploy configuration file stored on my used FS. So when I use it, all those components in launchers are deployed automatically. Thus for me they loose their value as launchers because I’m not going to remove those components from the system ever.
Now when I add my own launchers they are added to the same “default” launchers list and mixed with the ones that are there. So I have a mixed list of launchers that are effectively static with my custom ones that are effectively dynamic (I want to start and stop them at will) - it’s a bit of inconvenience.
Is there a way to remove those “default” launchers that are already part of my saved deploy file?
In short no. Launchers you’re using actively in your deploy file need to be part of /config/launcher/. The entries within the deploy configuration are referencing them, the content is read from those launcher files. If you want to shadow the content of it, you can save a modified version at the location @jschlatow already mentioned.
If you want to remove an unused launcher from your /config filesystem, you either need to compile Sculpt OS yourself (without the launcher selected), or you might dynamically delete the corresponding launcher files at startup (they are exported initially from the boot image into the /config filesystem).
