Initally some local site, then I transferred to GoDaddy, then to OVH (since GD is shit). One is still at Cloudflare (tried to move there, but they don’t support al TLDs that I use, like “.eu”).
For DNS I use Cloudflare. They provide a layer of privacy, i.e. your server IPs don’t get exposed directly.
I recently started using https://github.com/immich-app/immich
It’s basically a self hosted Google Photos and it’s working really well. You can just mount your heap of photos into the container, declare it as external library and you’re good to go.
After a few hours/days of training the face recognition, extracting meta data, generating thumbnails ans possibly transcoding videos you’ll have a very responsive and easily searchable timeline of ALL your pictures and videos.
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).
Why not renting a few machines and virtualizing yourself? Can you install ESXi on a Hetzner server?
Oh man, that’s actually really good advice! I recently switched to Vaultwarden, but you’re right: If my server goes down, I can’t even restart it, because the password for my account is in there! Damn! Close call!
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.
I learned a lot from the tutorials of https://ibracorp.io/
You’ll find rather advanced things there, but they are easy to follow and well explained.
Oh, I like that! Awesome, thank you!
They say that their format is open. In reality, it’s them who exclusively control the definition and further evolution of the format.
For as long as they continue to support and release code for open formats, there’s hardly an argument here.
That’s exactly the issue. We are dependent on Google’s goodwill and if they decide to scrap it or collect license fees for it we’re shit out of luck.
Could you elaborate on this please? Isn’t cloudflared a tunnel INTO the machine running a service? Can you use the same tunnel for outbound traffic as well?? Where does the traffic end up? How does this work?
I’m against using a Google OS (Android, Chrome OS), to browse on a Google regulated web (Manifest V3), based on a Google protocol (Protobuf) loading pages via Google proxies (Google AMP) filled with Google Ads displayed using a Google format (webp, webm), while everything is recorded and fingerprinted to update my Google Ad Profile.
No, thank you very much!
More open formats, more open Internet! Down with Google!
eMule
That’s where you could find everything!
Weird! It was late. This is what I use: https://blog.zazu.berlin/software/a-almost-perfect-rsync-over-ssh-backup-script.html
Yes, your uni might intercept communication on port 53 and reroute it to their DNS servers. It’s possible.
I used this one, with some modifications, like command line parameters to reuse it for different backup jobs.
I’ve packaged it into a little docker container that runs crond and runs the script every day for a few backup pairs.
I had UrBackup running for 6 months+. It wasn’t reliably backing things up, configuring it to be accessible via Internet is almost impossible, adding clienta is a hassle and the config isn’t very user friendly.
Furthermore I got the inpression, that it’s backups aren’t reliable; restoring files without UrBackup might be impossible.
That’s why I’m now back at a incremental rsync backup script. It’s reliable, you can just restore things by copying them back via ssh and it uses a lot less space (!!!) than the UrBackup backups.
Nah, use Mesh Central 2! It’s free, you can self-host it and using a little agent you can connect to any machine from it via console or even via a desktop interface without bothering with VNC etc.
Have a look at GitLab.
I’m doing the same thing you are doing, but automatically. I have a repo per app and a few GitLab runners connected on my Raspis/servers. Everytime I push a change, the shell runner runs the commands configured for the pipeline. I don’t have to lift a finger after changes.