Hi, why don’t you create a save button? Way easier compared to copy all option deploy child etc from /model to /rw/config/26.04 folder…
Are you able to make a more detailed proposal as to what you are specifically asking for? Are you wanting a more traditional GUI text editor to do the configuration files for instance? Is there an example from elsewhere that would help us visualize this?
Much of this stuff will hopefully come in time as more people use Sculpt and start to smooth out the rough edges. I think there is something about making configurations easier to edit in roadmaps / other goals if you want to read around the website.
2 Likes
Yes, I have a HDD so naturally when I download a component and I select to what it should be connected, I would like to easily safe the config I just tested so when I reboot I can find an already configured VM that just starts or need to be started.
For example I install Firefox VM let’s say… When downloaded it is there in my HHD but if I reboot I should re-configure it (what is the GUI, file system etc…). This is annoying and unnecessary and can be simply solved through terminal. But won’t be easier to say via GUI “do you want to maintain this configuration so the app will keep remaining in my Leitzentrale without to re-config it every time?”
I hope it is more clear, to get what I want it is possible to copy in rw deploy (this runs the app when I start the os maintaining them for ever on Leitzentrale.
An easy way to keep everything permanent
I believe you can turn any component you deployed into an “option” by creating an option file with the connections you need. So deploying it on the next boot becomes a matter of enabling the checkbox in the “options” menu.
Also by simply copying the deploy file you save your current system state, so on the next boot everything would be deployed as it was before reboot/shutdown without any explicit user action.
Does it look like what you need?
1 Like