Comment by j on "Maintaining system configuration across installations ( Linux - Ubuntu distro )."

hmm there several ways:

For example: stateful (puppet (provisioning client) + puppeteer (provisioning - server)) are things like puppet -> you save your puppet configuration and you system will be restored to this template. (ruby)

so you update your puppet configuration and your system will update as well as you got a meta representation of you configuration.

stateless ansible / fabric again same thing you can version it in git and trigger your setup via ansible script. They basically do the thing that Emil Moe mentioned but you can have it concurrent with results (python)

Those are just the top of my head things. And ofc I tend to put everything biznez related into a LXC container aka docker. But even here as moe mentioned it depends on your usecase as well as time and interest in this topic.

Mine is concurrent with results too because I execute 1 command at a time 😛 Although feedback is of course only given after the command finished since it's PHP.

Emil Moe I don't argue about your coding skills ;D I just point to the standard industry solutions :D esp correct concurrency handling with PHP is a pain in the ass if done properly -> registering the tick, the signal handling using PCNTL or eventLib and than implementing for example shmop for thread shared memory communciations.

or in fabric i add @parallel as a decorator command.

I am just lazy these days :)

Yeah I guess if it's this complex. I only have to boot up the server with software and some configuration and never touch it again with PHP. Maybe in the future logging in and executing an update except if I decide to do that by a crontask, I just don't feel so comfortable doing that.

Emil Moe I wouldn't either :D unless I test it daily ;D

Search Hashnode