Yes, another great solution.
A lot of people recommend Docker, but I will go further and say to specifically use Docker compose.
That way all the configuration is in a file that you can backup/restore. Updating is really easy, and you will never forget one of the random flags you need to set.
When they said, “Don’t write self modifying code”, they obviously didn’t mean me! /s
If you hate the taste of scrum give SAFe a try! (but really, please don’t)
The backend dev has seen into the depths of COBOL and JCL that keep the world from imploding.
And the code looked back.
Slackware was my first real distro (many moons ago), glad to see people still enjoy it.
Nope, what happens is segmentation fault
CORE DUMP FAILED, DISK OUT OF SPACE
I have Void running on my desktop, server, laptop, and media center. Then my NAS and router are running versions of FreeBSD (TrueNAS, Opnsense). Not really looking to change, so pretty happy overall.
I inject myself with beans every morning, usually French press
I have this exact problem.
Edit: nvm, found the solution
I’ve been using Void Linux for my home server for a few years now. It uses runit instead of OpenRC, and I haven’t had any problems with it. I would recommend the glibc version over the musl version.
Got 1 VM using KVM (Home Assistant), about a dozen docker containers, and a couple of services running on their own.
I feel like that is what snaps are for, long running server applications.
Been going through Advent of Code 2022 with lisp and have been having a great time.
I have liked onedev so far.
To add a couple of issues with Dynamic Libraries, and why someone would choose Static Libraries:
Like a lot of things, there are tradeoffs, and there is no universal correct choice.