I’ll see if I can publish some example configuration to github. Some friends are also asking 😅
It will be specific to my setup though. Tl;dr a linux server with Nginx reverse proxy. All services are spun up with docker compose and I have a static ip and domain to expose it on the internet which might be unnecessary for just home use.
You can DM me if you have any road blocks I can help with sooner.
I’ve got my server running on Windows and Radarr & Sonarr running on the same system. Data is stored on a NAS. I could move Radarr and Sonarr over to the NAS and setup docker with Overseerr.
I’ve never used docker so that is most of my initial worry.
Docker is relatively easy to use once you understand what it does.
The way it works can be simplified to - a way to package your app and its dependencies so it works out of the box on any machine that has a Docker Engine. When you run a docker container you specify what access it has to the underlying OS - file system, ports, etc.
A docker container essentially “thinks” it’s the only thing running on your OS unless you tell it otherwise.
Docker compose lets you spin up and configure multiple containers. Allows them to see each other on the network, share file access, etc. All of that happens declaratively in a docker compose file.
IMO it’s easier if your entire suite of apps is managed with compose.
I’ll see if I can publish some example configuration to github. Some friends are also asking 😅
It will be specific to my setup though. Tl;dr a linux server with Nginx reverse proxy. All services are spun up with docker compose and I have a static ip and domain to expose it on the internet which might be unnecessary for just home use.
You can DM me if you have any road blocks I can help with sooner.
I’ve got my server running on Windows and Radarr & Sonarr running on the same system. Data is stored on a NAS. I could move Radarr and Sonarr over to the NAS and setup docker with Overseerr.
I’ve never used docker so that is most of my initial worry.
Docker is relatively easy to use once you understand what it does.
The way it works can be simplified to - a way to package your app and its dependencies so it works out of the box on any machine that has a Docker Engine. When you run a docker container you specify what access it has to the underlying OS - file system, ports, etc.
A docker container essentially “thinks” it’s the only thing running on your OS unless you tell it otherwise.
Docker compose lets you spin up and configure multiple containers. Allows them to see each other on the network, share file access, etc. All of that happens declaratively in a docker compose file.
IMO it’s easier if your entire suite of apps is managed with compose.
You can read up on docker here.