Containers, the concept that Docker implements, lets app developers give a self-contained environment for distribution. For devs that means consistency in deployments across environments, which in turn means sysadmins can deploy each of these apps as fully isolated units.
With that, you get really clean installs/updates/uninstalls, and your deployments get done with a well-defined, declarative definition file which can also handle multi service dependencies (a la Docker Compose/K8s)
I find it funny it didn’t point out Active Directory
Ooh can I get an equivalent for zsh? :D
I’m genuinely having a chuckle at how shocked people are at my submission, made my day xD
To add on to this explanation, you generally use source ~/.bashrc
to reload your shell whenever you want to make changes to your user config. Tab completion weakens the barrier to destruction significantly (esp. in my case)
source ~/.bash_history
Would a LibreOffice environment suffice?
Dammit we’ve just made UPI
As an Indian myself this makes me happy :D
From a maintainability standpoint, absolutely. Computers have gotten fast enough to let programmers optimize for developer time instead
Ah I figured I had that one wrong, thanks!
Because systemd (the project) extends more than just systemd (the init system). It also includes things like:
and so many more
Now, in my personal opinion, I do find it good in that these being under one umbrella project led to fairly good integration between these aspects of “system management” as a whole. But I do also concede that this may feel like too many responsibilities handled by one project
Not particularly, most of my use has been on a desktop or laptop 😅
DWService is a favourite of mine. One self-contained program to run on the target, and a web-based interface to interact with it
It was initially intended to be a video stream handler, but they had concerns with audio syncing. They figured they might as well also handle audio in one cohesive AV server instead