Traefik with Seafile – My problems with labels and variables All the relevant labels required to pot forward and then the environment variables to set the SITE_URL and FILE_ROOT I recently moved from Nextcloud as my file syncing software to Seafile and so far have not looked back. Seafile is so much faster and the desktop clients are far more polished than Nextclouds solutions. I have setup Seafile pro with docker, however, I ran into several problems to do with Traefik labels.
Raspberry Pi – PiHole DNS Server NOTE: I had to disable the systemd-resolve service so that DNS requests where resolved by PiHole and not the default system service. $ sudo systemctl disable systemd-resolved.service $ sudo service systemd-resolved stop Running your own network wide DNS server can have its benefits. The reason for me setting this up is that I finally got fed up seeing large, in your face, adverts on my phone at home.
Docker-Compose - Traefik + More I run a small VPS (Virtual Private Server) for several services that I use e.g. a Git server, web servers etc.. As I began to add more and more services, I felt the need to separate these into self-contained blocks. Doing this meant that I could develop the applications on whichever platform I like and not worry about dependency mismatches. I made the decision to move my services to Docker.