Re:Run0 – systemd based alternative to sudo announced
by theteapot on Tuesday April 30, 2024 @06:52PM
(#40217436)
I think you mean systemctl.
Re:Run0 – systemd based alternative to sudo announced
by 8372049 on Tuesday April 30, 2024 @08:37PM
(#40218207)
He probably meant sysadmin as in the account with sudo access.
Re:Run0 – systemd based alternative to sudo announced
by BenjiWiebe on Tuesday April 30, 2024 @11:57PM
(#40219349)
s/sysctl/systemctl/
Re:Run0 – systemd based alternative to sudo announced
by berkes on Wednesday May 01, 2024 @02:51AM
(#40220304)
Correct. Typed it on mobile.
Re:Run0 – systemd based alternative to sudo announced
by eru on Wednesday May 01, 2024 @01:47AM
(#40219921)
Yes, we are moving more and more towards a system of immutable deployments.
That's good! We don't patch executable binaries these days: we just compile a new one from source, when we made a change. Similarly, more and more we just build new systems (or their images) from source, instead of mucking around with existing systems.
Ephemeral setups (amongst which k8s) remove that need but introduce a big load of other stuff.
Having a VPS that is managed by sysadmins (users with sudo rights, authed with keys) and on which partly overlapping "deploy" users can write to small parts and maybe do a passwordless "sudo sysctl restart fooapp" but only that, is a nice and simple setup.
I manage at least seven of these. And nothing in me even considers porting this to my k8s infra.
Edit: The reason for this setup is simple and twofold: deploy is safe and clear: deployers can be confident that whatever crap they pull, the server will churn on, data will be safe, recovery is possible. And all devs/ops having their own keys and accts gives a trail, logs and makes it very easy to remove that contractor after she did her work.