Git Product home page Git Product logo

ezarr's People

Contributors

bakerboy448 avatar emiliojorge avatar harmadasg avatar kwertyops avatar luctia avatar pavlogal avatar strahey avatar vvdaal avatar zknown avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

ezarr's Issues

Cannot set root path in sonarr and radarr due to permissons

Hi there.

Amazing piece of software you have here. This will probably turn into the go-to way to setup a servarr in the future due to its ease of use, especially due to the folder structures.

After using CLI and trying to set the root path on Sonarr for example, it cannot access the default data/media/tv path. The Sonarr log says -- Path: Folder is not writable by user abc
``
Looking at the permissions (in my case /home/username/servarr/data/media) by running ls -ltr,

I get

drwxrwxr-x 2 root root 4096 Jan 25 13:39 tv  

drwxrwxr-x 2 root root 4096 Jan 25 13:39 movies

Manually changing permissions of /home/username/servarr/data/media using sudo chown -R 13001 /home/username/servarr/data/media/tv seems to fix the issue.

Is this expected behavior?

Support for Overseerr

Describe the solution you'd like
It'd be nice if support for Overseerr was added.

Feature Request: Bridge Network

Is your feature request related to a problem? Please describe.
n/a

Describe the solution you'd like
Add a bridge network for the stack and assign all containers to that bridge network. That way all containers can use docker DNS and refer to each other by container name

Describe alternatives you've considered
n/a

Additional context
n/a

Feature request: CLI

Describe the solution you'd like
It'd be nice if all steps described in the README could be integrated into a single CLI tool where you'd be able to opt-in and -out of certain services without having to touch docker-compose.yml.

standard deployment support

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

unRAID support would be ideal. Deploying custom containers derived from your workspace with custom dockerfile/permissions/privelaged changes is still causing every error in the book it seems....

Describe the solution you'd like
A clear and concise description of what you want to happen.

unRAID/TrueNAS support with easy configuration for all apps including VPN/wireguard. An IBRACORP walkthrough after that is polished would also be nice.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

N/A

Additional context
Add any other context or screenshots about the feature request here.

N/A

question about data folder permissions

I'm in the process of modifying the instructions to install on a Synology NAS and I'm confused about line 28 in setup.sh
sudo chown -R $(id -u):mediacenter data/
Which user should be the owner here? Is it the regular Synology user? do they have to be a member of mediacenter?

same question for line 38
echo "UID=$(id -u)" >> .env

Support for sabnzbd

Describe the solution you'd like
It'd be nice if support for Sabnzbd was added.

Sonarr can't find root folder

I've followed the readme guide but I have encountered problems when it says :

Root folder: /data/media/ and then tv, movies or music depending on service

My sonarr can't find any folders inside /data/media so it doesn't let me use that as a root folder.
(My issue is similar to #14)

Support for Jellyseer

Is your feature request related to a problem? Please describe.
Jellyseer is a monitoring app for Jellyfin. Let's add support for it.

FlareSolverr support

support FlareSolverr to support prowlarr in the docker container would be awesome

Feature request: Windows support

Discussed in #30

Originally posted by boggsdabeast March 26, 2023
Hello there! I have a few questions related to setup that I couldn't find on the docs..

My host machine is Windows.. is that okay? If so, terminal is exiting your setup python after asking for file path. It's that expected?
Does host machine need to be Ubuntu/linux? Does your python need to be run in a Ubuntu/linux container?

Volume Mapping and documentation

I'm having a little bit of trouble understanding the documentation when it comes to media management and the qbittorrent management.

The documentation mentions the following points:

  • Root folder: /data/media/ and then tv, movies or music depending on service
  • 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 radarr category to /data/torrents/movies. You should do this.

However, when trying to add the root folders I can't seem to find the respective subfolders {tv,movies,music,books} as well as it doesn't allow me to add the data folder for some reason.

The same applies when configuring the folder on qbitorrent for a given category, for example, radarr gives me an error saying that it can't find /data/torrents/movies.

Am I supposed to change the volumes in the docker-compose.yml? I'm a bit lost here

Clean up and create templates for apps

Hi, I was going to add a new service to my local instance, but when looking at how to add it to the Python code I realized that there's a lot of room for improvement on the way configs are generated and parsed to create the docker-compose file.

I was curious if you'd have any interest in moving to something that uses a smaller config file to define apps/containers/env vars and other settings, and generalize the processor to output the final yaml from that, rather than having large chunks of static text that get parsed and merged.

It's not a ton of work, I can probably do a lot of the basic YAML editing and stake out an MVP for this over a few evenings, but I'm not sure if you'd want to go that route, so I figured I'd ask before I spend six hours coding something nobody else will use :)

Thanks for the project though, I've definitely gotten my money's worth out of it.

Baseline configuration files

Is your feature request related to a problem? Please describe.
Currently, the user still has to setup their configuration between the containers after initializing for the first time.

Describe the solution you'd like
Baseline configuration files could be added in order to make it easier to set up. Out of the box could perhaps be achieved.

How do you handle multiple media drives?

Nice project. Thanks for sharing it.

I have a few of these running in separate containers but as I'd like to add a few of the *arr services I'm considering replacing all of them with your setup here.

The one point I'm a bit unsure of is how you handle multiple media disks? At the moment I have containers running on a small ssd and then multiple hdds which store the media. I assume most people with home servers have a similar setup. So unless you have one enourmous ssd I'm wondering:

  • Do container performance not suffer on a hdd?
  • How do you add and structure other disks for media storage?

The current setup I have looks something like this:
Datadrive/docker/containers
Mediadrive1/film
Mediadrive2/tv
Mediadrive3/film
Mediadrive3/music

Since the current containers do not operate with one another all I had to do was include their drive paths in the dockercompose. With your setup I assume this would not work. Would you mind sharing an example of how I could handle this?

Thanks in advance.

Don't let people do a multi user install into their /home/user folder

Hi,

I do a lot of support for sonarr, radarr and all the many applications in one of these stacks. We're starting to have people show up on Discord having used your script to get going. But they're often storing their media and their docker configs in their ~/, but trying to do a multi user setup.

Can you fix this? The route I would go is if they choose a folder in their home folder, do a one user setup. If they pick a folder not in their home folder, like /docker for configs and /media for downloads and library do multi user. Or you could only allow multi user and block using /home.

Also, it feels like you're using UID in the 13000 range to try and avoid collisions. Why not just use the system's built in useradd and groupadd, then get those IDs to use?

VPN

As a user of an ezarr stack, id like to be able to utilize a vpn to encrypt only the torrent client traffic, so i have privacy and my ip provider will not be aware of the traffic

I'd like one of two options, a new vpn client service with the traffic from the torrent client routed through it or the torrent client service to include the openvpn client that can be configured appropriately.

Bazarr support

It'd be nice to add Bazarr, which manages and downloads subtitles for shows and movies added to Sonarr and Radarr.

Setup a support system like a Discord

It would also be great if you could setup a support system, like a Discord server or something.

Or maybe start hanging out on the sonarr/radarr discord and helping people that use ezarr?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.