2.2 KiB
2.2 KiB
EZARR
Ezarr is a project built to make it EZ to deploy a Servarr mediacenter, featuring:
- Sonarr
- Radarr
- Lidarr
- Prowlarr
- qBittorrent
- PleX
Using
- To get started, clone the repository in a directory of your choosing. Note: this will be where your installation and media will be as well, so think about this a bit.
- Copy
.env.sampleto a real.env:$ cp .env.sample .env. - Set the environment variables to your liking. Note that
ROOT_DIRshould be the directory you have cloned this in. - Run
setup.shas superuser. This will set up your users, a system of directories, ensure permissions are set correctly and sets some more environment variables for docker compose. - Run
docker compose up
That's it! Your containers are now up and you can continue to set up the settings in them. Take note of the following:
- When linking one service to another, remember to use the container name instead of
localhost. - Please set the settings of the -arr containers as soon as possible to the following (use
advanced):
- Media management:
- Use hardlinks instead of Copy:
true - Root folder:
/data/media/and then tv, movies or music depending on service
- Use hardlinks instead of Copy:
- Media management:
- In qBittorrent, after connecting it to the -arr services, you can indicate it should move
torrents in certain categories to certain directories, like torrents in the
radarrcategory to/data/torrents/movies. You should do this. Also set theDefault Save Pathto/data/torrents. Set "Run external program on torrent completion" to true and enter this in the field:chmod -R 775 "%F/". - You'll have to add indexers in Prowlarr by hand. Use Prowlarrs settings to connect it to the other -arr apps.
FAQ
Why do I need to set some settings myself, can that be added?
Some settings, particularly for the Servarr suite, are set in databases. While it might be possible to interact with this database after creation, I'd rather not touch these. It's not that difficult to set them yourself, and quite difficult to do it automatically. For other containers, configuration files are automatically generated, so these are more easily edited, but I currently don't believe this is worth the effort.