mhzawadi

I would start with a Debian os base, install docker and turn it into a swarm manager. Then look at stacks and how services work, if you find your running your host too hard. You can add a work host and stread out.

Once you have docker swarm running, get portainer running. I use portainer as a visual whats happening on my swarm, but I use the docker cli to start and update all my stacks. I have my stacks in a git repository so that I have a backup and history of what changes I did.

Now your a docker master, of sorts.

Your compose file will pull the image when you run it, from the registry it's in

on that update train right now

I have all external mounts in /mnt, if my container needs to use it then it's in the compose file to use the local mount.

All my compose and stacks are in a git repo, the repo lives in my home dir and pulled fromy Gogs server. That only I can access.

can we all chip in and get one sent to Trump as a welcome gift?

can confirm nextcloud news alpha is great, as is the mobile app

Thats how I had my setup run, point the volume at NFS

If you have your services in compose files, you can point the volumes to anywhere. Even NFS.

Like the below config

volumes:
   pihole01:
    driver: local
    driver_opts:
      type: 'none'
      o: 'bind'
      device: '/mnt/data/docker/pihole01'

I think you can make a template from the helpers page, see if that works

I run my own server, not sure on post retention or image size or even number of images. But you can make it so that only you can make communities, you can even make communities admin post only.

I would give the docs a good read and maybe have a look at the GitHub repos

oh, I miss understood how it works. will have a play

do you have a docker image I can play with?