Went from a brand-new domain to a fully-functional secure self-hosted email system that gmail happily accepts mail from, with webmail and an LDAP user database I can wire other shit into, in a couple of hours work.
Damn I'm good.

oh god how did this get here i am not good with computer

.png)
Background music:
Click here because I can't put an audio widget in the profile
The scenes with the shark are usually very intense and disturbing.
I use Arch BTW
Fun fact: Neo-Nazi dipshit cartoonist Stonetoss is in fact Hans Kristian Graebener of Spring, Texas
Went from a brand-new domain to a fully-functional secure self-hosted email system that gmail happily accepts mail from, with webmail and an LDAP user database I can wire other shit into, in a couple of hours work.
Damn I'm good.
I could write something up. The problem is all my systems are bespoke and this is the second "biggest" setup I've ever made (and in the course of about four hours instead of bits and pieces over a few weeks... also bearing in mind it's about seven orders of magnitude smaller in terms of users than the stuff I get paid to work on), but a basic walkthrough would basically be like... let's see...
Yeah, that's straightforward enough, I could write something like that up...
Okay yeah I'm working on this but writing documentation is slow going lmao.
I think I read somewhere you have A Dislike of ansible, do you like anything ansible-like to make this a script?
Eh? I don't have anything against Ansible, I've just never used it... You might be thinking of my general dislike of Docker and k8s which is not that I dislike them as technologies but I dislike the attitude that any system has to be built using them or similar orchestration systems so that it can Scale, when it just makes administration and management harder and adds a bunch of bloat when you're just trying to learn stuff and build out a small hobby or self-managed system. k8s is definitely the least worst of many options for managing a large fleet.
I could probably write an Ansible playbook once I'm done writing up the documentation although a big part of the old school approach I'm using is as a more flexible exercise, ie "if I understand the thing well enough I can set it up on any system using native packages". But yeah once I'm done writing up a HOWTO I could slop a playbook or something together