• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle







  • Do NOT self-host email! In the long run, you’ll forget a security patch, someone breaches your server, blasts out spam and you’ll end up on every blacklist imaginable with your domain and server.

    Buy a domain, DON’T use GoDaddy, they are bastards. I’d suggest OVH for European domains or Cloudflare for international ones.

    After you have your domain, register with “Microsoft 365” or “Google Workspace” (I’d avoid Google, they don’t have a stable offering) or any other E-Mail-Provider that allows custom domains.

    Follow their instructions on how to connect your domain to their service (a few MX and TXT records usually suffice) and you’re done.

    After that, you can spin up a VPS and try out new stuff and connect it also to your domain (A and CNAMR records).



  • Media Server? No content backup at all.

    If you lose everything, just download new stuff you want to watch, or redownload a few TV series/movies.

    Music? There are streaming services.

    Only backup configurations and maybe application data, so that the reinstall will be easy. Those few kB/MB could sit anywhere. I’m using GitLab for this purpose.

    Edit: Images! If you have your photos on there, back them up! They can’t be replaced!







  • The thing is it’s not really a “documentation” but just a collection of configs.

    I have organized my containers in groups like you did (“arrs”, web server, bitwarden, …) and then made a repository for each group.

    Each repository contains at least a compose file and a Gitlab CI file where a aimple pipeline is defined with basically “compose pull” and “compose up”. There are alao more complicated repository where I build my own image.

    The whole “Git” management is really transparent, because with Gitlab you can edit directly on the platform in a hosted VSCode environment where you can directlY edit your files and when your satisfied you just press commit. I don’t do weird stuff with branches, pushing and pulling at all. No need for local copies of the repository.

    If you want to fulltext search all your repos, I can recommend a “Sourcegraph” container, but use version 4.4.2 because starting with 4.5.0 they have limited the number of private reositories to 1. But this is something for later, when your infrastructure has grown.


  • I’m defining my service containers via GitLab and I deploy them via tagged and dockerized GitLab Runners.

    If something fails, I change the runner tags for a service and it will be deployed on a different machine.

    Incl case of a critical failiure, I just need to setup a Debian, install docker, load and run the GL runner image, maybe change some pipelines and rerun the deployment jobs.

    Some things aren’t documented well, yet. Like VPN config…

    Ah yes, my router is able to access GitLab as well and pull the list of static routes etc. from it.