Your compose file will pull the image when you run it, from the registry it’s in
I run this server
Your compose file will pull the image when you run it, from the registry it’s in
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 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 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?
I use Jellyfin, moved from subsonic and its amazing
no, its a different thing
That sounds like a great plan, and a great way to learn how this sort of thing works.
I use passkeys and find them great, mind you I know that you need at least 2 of them so you have a backup. I also use yubikeys at work and they are the same issue, you need 2 of them in case 1 breaks or gets lost.
Maybe the setup should be, make sure you have 2 passkeys on 2 different devices? but not in your password manager
Have a look at OVH, they have very good VPS prices
Why not a private Lemmy instance?
I used TVHeadend in OSMC and found it a pig to setup at first, but it works great once you have it all setup
I have a single network with my jellyfin server and wifi devices, I run Pi-Hole with DNS for internal things and can use Jellyfin while at home or out and about.
In Pi-Hole look for Local DNS Records
to add your own suff
maybe its just me, but self hosting is more about learning to run and then simplify my setup. Thats why I read the documentation for the project I want to deploy, then see if I have anything that looks similar. But as I’ve been doing self hosting for almost 20 years, plus working at a SaaS company. I have done a lot of things with a lot of different tech
All my docker stuff has a very common look to it, also I have tried a lot of stuff. See my Git repo with some examples -> https://github.com/mhzawadi/docker-stash
have made a start in documenting what I run, not sure who much of how it runs you want
have made a start in documenting what I run, not sure who much of how it runs you want
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.