Reset history to current sanitized state
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
# Prowlarr
|
||||
|
||||
Prowlarr centrally manages indexers and synchronizes them with supported download and media-management
|
||||
applications.
|
||||
|
||||
## Deployment layout
|
||||
|
||||
- **Compose:** `/srv/docker/prowlarr/docker-compose.yml`
|
||||
- **Static configuration/source:** no additional mounted static configuration
|
||||
- **Non-secret environment:** UID `1000`, GID `1000`, timezone `Etc/UTC`, and restrictive umask `0077` are
|
||||
declared inline in Compose
|
||||
- **Secrets:** no separately mounted secret file; the application-generated API key is stored inside the
|
||||
protected Prowlarr application state
|
||||
- **NVMe application state:** `/srv/appdata/prowlarr/config`
|
||||
- **Bulk HDD data:** none
|
||||
- **Other mounts:** none
|
||||
|
||||
Secrets are never committed to this repository. Prowlarr manages its API key
|
||||
inside `/srv/appdata/prowlarr/config/config.xml`; the complete application-state
|
||||
directory and its backups must therefore be treated as sensitive.
|
||||
|
||||
## Dependencies and recovery
|
||||
|
||||
- **Networks/dependencies:** Prowlarr uses the external `npm_proxy` network at `192.168.97.21`; indexers and
|
||||
integrations with download or media-management applications are configured in its protected application state
|
||||
- **Back up:** `/srv/appdata/prowlarr/config`, including its database and sensitive application configuration
|
||||
- **Re-creatable:** the Prowlarr container image; no separate persistent cache is declared
|
||||
Reference in New Issue
Block a user