More moaning about #linux.

[paco@infosec.exchange]

More moaning about #linux. I'm trying to get a discourse server off the ground. Why the fuck do they insist on installing non-OS stuff in the middle of all the OS stuff.

/var/discourse is not a good default. And then fucking docker wants to be /var/lib/docker. Never mind how /var/lib doesn't make any goddamn sense.

Related to my earlier discussion of hard drive partitioning. What I would like to do is have a volume that is not the operating system, but is instead all the application data. The discourse data, database, assets people upload, etc. That way I can have this nice virtual disk that encapsulates it. I could theoretically build a new node, attach this drive to the new node, and migrate the site. I can snapshot that drive more frequently than, say, the OS drive. Lots of benefits to encapsulating it.

[paco@infosec.exchange]

But no. The discourse "easy installer" sprays shit all over /var. I'm gonna get some database down in /var/lib/docker/something and I'm going to get assets living in /var/discourse, and umpteen gajillion container images in /var/lib/docker.

But I also have fucking /var/log for OS logs, and /var/run for runtime information like PIDs, and /var/lock and /var/tmp. I think /var/most-important-app-on-the-system is NOT where you put application software. So my volume/filesystem to encapsulate discourse? Is that a big ass /var?

I love #FreeBSD because it is so well organized. They even go to trouble to make packages like postfix or apache fit the idiom, rather than let it install in /var/lib/opt/sbin/etc or some shit.

This public service announcement sponsored by Old Man Yells at Cloud, Inc.

[chris@mstdn.chrisalemany.ca]

@paco this is also important to me. 👊

[julian@activitypub.space]

@paco@infosec.exchange why Discourse?

Use NodeBB. We keep our shit in one folder.

You can put that folder anywhere 🫠