sct
5ff8ae32ec
|
4 years ago | |
---|---|---|
.github | 4 years ago | |
.vscode | 4 years ago | |
config | 4 years ago | |
public | 4 years ago | |
server | 4 years ago | |
src | 4 years ago | |
.dockerignore | 4 years ago | |
.editorconfig | ||
.eslintrc.js | 4 years ago | |
.gitignore | 4 years ago | |
.prettierignore | 4 years ago | |
Dockerfile | 4 years ago | |
Dockerfile.local | ||
LICENSE | 4 years ago | |
README.md | 4 years ago | |
babel.config.js | 4 years ago | |
docker-compose.yml | ||
next-env.d.ts | ||
next.config.js | 4 years ago | |
ormconfig.js | 4 years ago | |
overseerr-api.yml | 4 years ago | |
package.json | 4 years ago | |
postcss.config.js | ||
stylelint.config.js | 4 years ago | |
tailwind.config.js | 4 years ago | |
tsconfig.json | 4 years ago | |
yarn.lock | 4 years ago |
README.md
Overseerr is a libre software tool for managing requests for your media library. It integrates with existing services such as Sonarr and Radarr!
Current Features
- Full Plex integration. Login and manage user access with Plex!
- Integrates easily with your existing services. Currently Overseerr supports Sonarr and Radarr. More to come!
- Syncs to your Plex library to know what titles you already have.
- Complex request system allowing users to request individual seasons or movies in a friendly, easy to use UI.
- Incredibly simple request management UI. Don't dig through the app to simply approve recent requests.
- Granular permission system
- Mobile friendly design, for when you need to approve requests on the go!
In Development
- User profiles.
- User settings page (to give users the ability to modify their Overseerr experience to their liking).
- Version update notifications in-app.
Planned Features
- More notification types (Slack/Telegram/etc.).
- Issues system. This will allow users to report issues with content on your media server.
- Local user system (for those who don't use Plex).
- Compatiblity APIs (to work with existing tools in your system).
Running Overseerr
Currently, Overseerr is only distributed through Docker images. If you have Docker, you can run Overseerr as per:
docker run -d \
-e LOG_LEVEL=info \
-e TZ=Asia/Tokyo \
-p 5055:3000 \
-v /path/to/appdata/config:/config \
--restart unless-stopped \
sctx/overseer
After running Overseerr for the first time, configure it by visiting the web UI at http://[address]:5055 and completing the setup steps.
⚠️ Overseerr is currently under very heavy, rapid development and things are likely to break often. We need all the help we can get to find bugs and get them fixed to hit a more stable release. If you would like to help test the bleeding edge, please use the image sctx/overseerr:develop instead! ⚠️
Preview
Support
- You can get support on Discord.
- Bugs can be opened via a GitHub issue.
API Documentation
Full API documentation will soon be published automatically and available outside of running the app. Currently, you can access the API docs by running Overseerr locally and visiting http://localhost:3000/api-docs
Contribution
Anyone is welcome to contribute to Docker, and pull requests are greatly appreciated!
Contributors
Developing Overseerr
You can develop Overseer entirely in Docker. Make sure you have Docker Desktop installed before continuing.
- Make sure you have Docker Desktop installed.
- Run
docker-compose up -d
to start the server. - Access the container at http://localhost:3000
If Docker isn't your jam, you can always run Overseer with these Yarn commands:
yarn
yarn dev
You will need Node.js installed. Once it's built and running, access it locally at http://localhost:3000 (just like Docker).
Translation
We use Weblate for our translations so please feel free to contribute to localizing Overseerr!