Impressive deep dive on breaking away from serverless lock-in. The daemon(8) wrapper aproach is really clever for getting all those service management features without retrofitting your code. That log rotation section with SIGHUP handling clarified somethig I'd been confused about for years, honestly didnt realize the file handle semantics made that necesary. Your point about FreeBSD's stability vs cloud provider upgrade treadmill is underrated too.
Nice read, I thought about doing something similar. Just to compare notes, are you compiling on the server directly or do you cross compile? Does it means you setup a ssh on the server? I found jails less convenient that podman with systems
I build natively on the same server for now. Not ideal but it's good enough for me. (Ideally I'd set up a separate VM with bhyve for the services, but that seems like a big hassle maintainance-wise...)
Impressive deep dive on breaking away from serverless lock-in. The daemon(8) wrapper aproach is really clever for getting all those service management features without retrofitting your code. That log rotation section with SIGHUP handling clarified somethig I'd been confused about for years, honestly didnt realize the file handle semantics made that necesary. Your point about FreeBSD's stability vs cloud provider upgrade treadmill is underrated too.
Nice read, I thought about doing something similar. Just to compare notes, are you compiling on the server directly or do you cross compile? Does it means you setup a ssh on the server? I found jails less convenient that podman with systems
I build natively on the same server for now. Not ideal but it's good enough for me. (Ideally I'd set up a separate VM with bhyve for the services, but that seems like a big hassle maintainance-wise...)