shaunjanssens

joined 11 months ago
sorted by: new top controversial old
1
Docker back-up strategy (alien.top)
 

I know, and read, a lot of posts here about backing up Docker volumes and data. The problem is that everyone has different setup, context and needs. So I need some help deciding what is best (and easy to manage) solution for my use case.

My setup is fairly simple. I only use docker compose files, have one service per directory and all services are using named volumes. Some have driver: local to mount a local folder with config (always located in the same directory of the service). Each docker-compose.yaml file has a backup container which is offen/docker-volume-backup to backup the volumes. These backups are stored in a different folder (the same for all backups /media/storage/backups/). I also have a service with Duplicati to backup the volume backups and some extra data (Nextcloud) to a remote server.

The reason why I use offen/docker-volume-backup is to shut down some containers for extra safety but I'm not sure I actually need this because I'm the only user and I'm not planning on opening my server for other user.

Before I implemented docker-volume-backup and Duplicati all containers used bind mounts because that's less abstract for me, to actually see the files.

Now, my question is: is this a good setup? Is there an easier setup with less components/steps? Is it, for example, also good if I go back to bind mounts and just backup everything with Duplicati when I'm asleep at night?

Thank you for all the great advise!

Advice on remote access to media stack. in c/main@selfhosted.forum
[–] shaunjanssens@alien.top 1 points 11 months ago

You're missing the easiest option of them all: Cloudflare tunnels. You don't have to open any ports, your friends don't need to install extra software and it's free. I don't know about the TOS but I wouldn't worry to much because it's only a couple of friends.

I don't fully understand how/why you guys selfhost some apps in c/main@selfhosted.forum
[–] shaunjanssens@alien.top 1 points 11 months ago

For me it's mainly the fun. I'm less privacy minded than other people here but I'm sure that I will be happy to own all my data at some point in time.

Looking for suggestions to limit access to a public self-hosted page in c/main@selfhosted.forum
[–] shaunjanssens@alien.top 1 points 11 months ago (1 children)

I'm using Cloudflare Applications (part of Zero Trust) for this. You can add multiple login methods (email, Google, Facebook, Github, ect) and also IP addresses. I think it's also possible to accept someone when they request access. It's very easy to set-up and will also prevent brute force attacks. You can protect a whole application but it's also possible to protect specific paths.

My first steps into self hosting and my homelab dashboard in c/main@selfhosted.forum
[–] shaunjanssens@alien.top 1 points 11 months ago

It's crazy! I'm really looking forward to tinker with it every time I'm done working!

Thanks for the correction! English is not my mother tongue.

My first steps into self hosting and my homelab dashboard in c/main@selfhosted.forum
[–] shaunjanssens@alien.top 1 points 11 months ago

Thank you for all the kind words! It would be much appreciated to get some feedback!

1
My first steps into self hosting and my homelab dashboard (alien.top)
 

Homer dashboard with custom theme

After lurking for years on this subreddit I finally bought a mini PC for the soul purpose of experimenting with self hosting. So the past few days I've been learning about Docker and stealing all your docker-compose files and combined them into something I could actually use.

The code is available on Github. Please give me some feedback because I'm 200% sure I did a lot the wrong way. What I've however learned from you guys is to document what you're doing when you're doing it instead of later (never).