If you’re already self-hosting:
Document your setup. Write guides. Make it easier for the next person.
Heck yeah! This is exactly what I’m trying to do: codeberg.org/lch361/infrastructure.lch361.net (in the future I’m planning to move all code to a self-hosted Forgejo service, especially when it’ll implement federation). Infrastructure as code, performance metrics, automation - it’s all there. It’s not just a matter of self-hosting and privacy anymore. It’s an effort to make the engineering behind that more approachable.