this post was submitted on 02 Apr 2025
340 points (98.9% liked)
linuxmemes
24401 readers
597 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. 🇬🇧 Language/язык/Sprache
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Workstation-as-code is pretty dope for enterprise...
The idea of an immutable, idempotent, declarative workstation, from cradle to grave, tickles me pink.
At that point, make it a thin client which boots from a network image and logs you into a terminal server.
Then you have the hardware and software resources you need for your role wherever you are.
This sounds like a great idea until you have multiple physical sites and dhcp doesn’t span network segments. Or, even if you’re willing to deal with that, employees who work from home. Anything that solves for the second one is almost certainly more complicated than just using vms or containers on remote workstations or a configuration manager on the workstation os and not waste your time on the thin client part
So... containers that people log into...? Falls under containers