Bump actions/setup-python from 5 to 6

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5 to 6.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](https://github.com/actions/setup-python/compare/v5...v6)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-version: '6'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -53,5 +53,5 @@ YOUR CONFIG HERE
 ```
 
  - [ ] I understand, that without logs and/or screenshots and a detailed description of the problem, it is very hard to fix bugs.
- - [ ] I have checked the [documentation](https://maxdorninger.github.io/MediaManager/introduction.html) for help.
+ - [ ] I have checked the [documentation](https://maxdorninger.github.io/MediaManager/) for help.
  - [ ] I have searched the [issues](https://github.com/maxdorninger/MediaManager/issues) for similar issues and found none.

.github/dependabot.yml

@@ -0,0 +1,25 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+
+  - package-ecosystem: "npm"
+    directory: "/web"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+
+  - package-ecosystem: "uv"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+

.github/workflows/build-docs.yml

@@ -1,139 +0,0 @@
-name: Build documentation
-
-on:
-  push:
-    branches: [ "master" ]
-    paths:
-      - 'Writerside/**'
-      - '.github/workflows/build-docs.yml'
-  workflow_dispatch:
-
-permissions:
-  contents: read
-  id-token: write
-  pages: write
-
-env:
-  INSTANCE: 'Writerside/mm'
-  DOCKER_VERSION: '2025.04.8412'
-  ALGOLIA_APP_NAME: '5SXJTW5J6S'
-  ALGOLIA_INDEX_NAME: 'MediaManagerDocs'
-  CONFIG_JSON_PRODUCT: 'MM'
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    outputs:
-      algolia_artifact: ${{ steps.define-ids.outputs.algolia_artifact }}
-      artifact: ${{ steps.define-ids.outputs.artifact }}
-    steps:
-      - name: Checkout repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 0
-
-      - name: Define instance id and artifacts
-        id: define-ids
-        run: |
-          INSTANCE=${INSTANCE#*/}
-          INSTANCE_ID_UPPER=$(echo "$INSTANCE" | tr '[:lower:]' '[:upper:]')
-          ARTIFACT="webHelp${INSTANCE_ID_UPPER}2-all.zip"
-          ALGOLIA_ARTIFACT="algolia-indexes-${INSTANCE_ID_UPPER}.zip"
-
-          # Print the values
-          echo "INSTANCE_ID_UPPER: $INSTANCE_ID_UPPER"
-          echo "ARTIFACT: $ARTIFACT"
-          echo "ALGOLIA_ARTIFACT: $ALGOLIA_ARTIFACT"
-
-          # Set the environment variables and outputs
-          echo "INSTANCE_ID_UPPER=$INSTANCE_ID_UPPER" >> $GITHUB_ENV
-          echo "ARTIFACT=$ARTIFACT" >> $GITHUB_ENV
-          echo "ALGOLIA_ARTIFACT=$ALGOLIA_ARTIFACT" >> $GITHUB_ENV
-          echo "artifact=$ARTIFACT" >> $GITHUB_OUTPUT
-          echo "algolia_artifact=$ALGOLIA_ARTIFACT" >> $GITHUB_OUTPUT
-
-      - name: Build docs using Writerside Docker builder
-        uses: JetBrains/writerside-github-action@v4
-        with:
-          instance: ${{ env.INSTANCE }}
-          docker-version: ${{ env.DOCKER_VERSION }}
-
-      - name: Save artifact with build results
-        uses: actions/upload-artifact@v4
-        with:
-          name: docs
-          path: |
-            artifacts/${{ steps.define-ids.outputs.artifact }}
-            artifacts/report.json
-            artifacts/${{ steps.define-ids.outputs.algolia_artifact }}
-          retention-days: 7
-  test:
-    needs: build
-    runs-on: ubuntu-latest
-    steps:
-      - name: Download artifacts
-        uses: actions/download-artifact@v4
-        with:
-          name: docs
-          path: artifacts
-
-      - name: Test documentation
-        uses: JetBrains/writerside-checker-action@v1
-        with:
-          instance: ${{ env.INSTANCE }}
-  deploy:
-    environment:
-      name: github-pages
-      url: ${{ steps.deployment.outputs.page_url }}
-    needs: [ build, test ]
-    if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
-    runs-on: ubuntu-latest
-    steps:
-      - name: Download artifacts
-        uses: actions/download-artifact@v4
-        with:
-          name: docs
-          path: artifacts
-
-      - name: Unzip artifact
-        run: unzip -O UTF-8 -qq "artifacts/${{ needs.build.outputs.artifact }}" -d dir
-
-      - name: Setup Pages
-        uses: actions/configure-pages@v4
-
-      - name: Package and upload Pages artifact
-        uses: actions/upload-pages-artifact@v3
-        with:
-          path: dir
-
-      - name: Deploy to GitHub Pages
-        id: deployment
-        uses: actions/deploy-pages@v4
-  publish-indexes:
-    needs: [ build, test, deploy ]
-    runs-on: ubuntu-latest
-    if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
-    container:
-      image: registry.jetbrains.team/p/writerside/builder/algolia-publisher:2.0.32-3
-    steps:
-      - name: Download artifact
-        uses: actions/download-artifact@v4
-        with:
-          name: docs
-          path: artifacts
-      - name: Unzip Algolia artifact
-        run: unzip -O UTF-8 -qq "artifacts/${{ needs.build.outputs.algolia_artifact }}" -d algolia-indexes
-      - name: Update Algolia Index
-        run: |
-          if [ -z "${{ secrets.ALGOLIA_KEY }}" ]; then
-            echo "ALGOLIA_KEY secret is not set in GitHub Secrets"
-            exit 1
-          else
-            env "algolia-key=${{ secrets.ALGOLIA_KEY }}" java -jar /opt/builder/help-publication-agent.jar \
-            update-index \
-            --application-name ${{ env.ALGOLIA_APP_NAME }} \
-            --index-name ${{ env.ALGOLIA_INDEX_NAME }} \
-            --product ${{ env.CONFIG_JSON_PRODUCT }} \
-            --index-directory algolia-indexes/ \
-            2>&1 | tee algolia-update-index-log.txt
-          fi

.github/workflows/docs.yml

@@ -0,0 +1,62 @@
+name: Publish docs via GitHub Pages
+on:
+  push:
+    branches:
+      - master
+    tags:
+      - v*
+  workflow_dispatch:
+    inputs:
+      set_default_alias:
+        description: 'Alias to set as default (e.g. latest, master)'
+        required: false
+        default: 'latest'
+
+permissions:
+  contents: write
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Configure Git Credentials
+        run: |
+          git config user.name github-actions[bot]
+          git config user.email 41898282+github-actions[bot]@users.noreply.github.com
+
+      - uses: actions/setup-python@v6
+        with:
+          python-version: 3.x
+
+      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
+
+      - uses: actions/cache@v4
+        with:
+          key: mkdocs-material-${{ env.cache_id }}
+          path: .cache
+          restore-keys: |
+            mkdocs-material-
+
+      - name: Install dependencies
+        run: pip install mkdocs-material mike
+
+      - name: Deploy (master)
+        if: github.ref == 'refs/heads/master'
+        run: |
+          mike deploy --push --update-aliases master
+
+      - name: Deploy (tag)
+        if: startsWith(github.ref, 'refs/tags/v')
+        run: |
+          version=${GITHUB_REF#refs/tags/}
+          mike deploy --push --update-aliases $version latest --title "$version"
+          mike set-default --push latest
+
+      - name: Set Default (Manual)
+        if: github.event_name == 'workflow_dispatch' && github.event.inputs.set_default_alias != ''
+        run: |
+          mike set-default --push ${{ github.event.inputs.set_default_alias }}

.gitignore

@@ -49,5 +49,5 @@ __pycache__
 # Postgres
 /postgres
 
-# Node modules
-/node_modules/*
+# MkDocs
+site/

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+97409287+maxdorninger@users.noreply.github.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -18,7 +18,7 @@ Generally, if you have any questions or need help on the implementation side of
 just ask in the issue, or in a draft PR.
 
 Also, see the contribution guide in the docs for information on how to setup the dev environment:
-https://maxdorninger.github.io/MediaManager/developer-guide.html
+https://maxdorninger.github.io/MediaManager/
 
 ### For something that is a one or two line fix:
 

Dockerfile

@@ -13,7 +13,7 @@ RUN env PUBLIC_VERSION=${VERSION} PUBLIC_API_URL=${BASE_PATH} BASE_PATH=${BASE_P
 FROM ghcr.io/astral-sh/uv:python3.13-trixie-slim AS base 
 
 RUN apt-get update && \
-    apt-get install -y ca-certificates bash libtorrent21 gcc bc locales postgresql media-types mailcap curl gzip unzip tar 7zip bzip2 unar && \
+    apt-get install -y ca-certificates bash libtorrent21 gcc bc locales postgresql media-types mailcap curl gzip unzip tar 7zip bzip2 unar gosu && \
     apt-get clean && \
     rm -rf /var/lib/apt/lists/*
 
@@ -33,7 +33,6 @@ RUN chown -R mediamanager:mediamanager /app
 
 USER mediamanager
 
-# Set uv cache to a writable home directory and use copy mode for volume compatibility
 ENV UV_CACHE_DIR=/home/mediamanager/.cache/uv \
     UV_LINK_MODE=copy
 
@@ -47,6 +46,7 @@ ARG BASE_PATH=""
 LABEL author="github.com/maxdorninger"
 LABEL version=${VERSION}
 LABEL description="Docker image for MediaManager"
+USER root
 
 ENV PUBLIC_VERSION=${VERSION} \
     CONFIG_DIR="/app/config" \

README.md

@@ -1,7 +1,7 @@
 <br />
 <div align="center">
-  <a href="https://maxdorninger.github.io/MediaManager">
-    <img src="https://raw.githubusercontent.com/maxdorninger/MediaManager/refs/heads/master/Writerside/images/logo.svg" alt="Logo" width="260" height="260">
+  <a href="https://maxdorninger.github.io/MediaManager/">
+    <img src="https://raw.githubusercontent.com/maxdorninger/MediaManager/refs/heads/master/web/static/logo.svg" alt="Logo" width="260" height="260">
   </a>
 
 <h3 align="center">MediaManager</h3>
@@ -9,7 +9,7 @@
   <p align="center">
     Modern management system for your media library
     <br />
-    <a href="https://maxdorninger.github.io/MediaManager/introduction.html"><strong>Explore the docs »</strong></a>
+    <a href="https://maxdorninger.github.io/MediaManager/"><strong>Explore the docs »</strong></a>
     <br />
     <a href="https://github.com/maxdorninger/MediaManager/issues/new?labels=bug&template=bug_report.md">Report Bug</a>
     &middot;
@@ -18,26 +18,24 @@
 </div>
 
 
-MediaManager is modern software to manage your TV and movie library. It is designed to be a replacement for Sonarr,
-Radarr, Overseer, and Jellyseer.
-It supports TVDB and TMDB for metadata, supports OIDC and OAuth 2.0 for authentication and supports Prowlarr and
-Jackett.
-MediaManager is built first and foremost for deployment with Docker, making it easy to set up.
+MediaManager is the modern, easy-to-use successor to the fragmented "Arr" stack. Manage, discover, and automate your TV and movie collection in a single, simple interface.
 
-It also provides an API to interact with the software programmatically, allowing for automation and integration with
-other services.
+Key features:
+- support for OAuth/OIDC
+- support for TVDB and TMDB
+- made to be deployed with Docker
 
 ## Quick Start
 
 ```sh
-wget -O docker-compose.yaml https://raw.githubusercontent.com/maxdorninger/MediaManager/refs/heads/master/docker-compose.yaml   
+wget -O docker-compose.yaml https://github.com/maxdorninger/MediaManager/releases/latest/download/docker-compose.yaml
 mkdir config
-wget -O ./config/config.toml https://raw.githubusercontent.com/maxdorninger/MediaManager/refs/heads/master/config.example.toml   
+wget -O ./config/config.toml https://github.com/maxdorninger/MediaManager/releases/latest/download/config.example.toml
 # you probably need to edit the config.toml file in the ./config directory, for more help see the documentation
 docker compose up -d
 ```
 
-### [View the docs for installation instructions and more](https://maxdorninger.github.io/MediaManager/configuration-overview.html#configuration-overview)
+### [View the docs for installation instructions and more](https://maxdorninger.github.io/MediaManager/)
 
 ## Support MediaManager
 
@@ -62,7 +60,7 @@ docker compose up -d
 <a href="https://buymeacoffee.com/maxdorninger"><img src="https://cdn.buymeacoffee.com/uploads/profile_pictures/default/v2/DEBBB9/JO.png" width="80px" alt="Josh" /></a>&nbsp;&nbsp;
 <a href="https://buymeacoffee.com/maxdorninger"><img src="https://cdn.buymeacoffee.com/uploads/profile_pictures/2025/11/2VeQ8sTGPhj4tiLy.jpg" width="80px" alt="PuppiestDoggo" /></a>&nbsp;&nbsp;
 <a href="https://github.com/seferino-fernandez"><img src="https://avatars.githubusercontent.com/u/5546622" width="80px" alt="Seferino" /></a>&nbsp;&nbsp;
-
+<a href="https://buymeacoffee.com/maxdorninger"><img src="https://cdn.buymeacoffee.com/uploads/profile_pictures/default/v2/EC9689/SY.png" width="80px" alt="syn" /></a>&nbsp;&nbsp;
 
 ## Star History
 
@@ -83,7 +81,7 @@ docker compose up -d
 
 ## Developer Quick Start
 
-For the developer guide see the [Developer Guide](https://maxdorninger.github.io/MediaManager/developer-guide.html).
+For the developer guide see the [Developer Guide](https://maxdorninger.github.io/MediaManager/).
 
 <!-- LICENSE -->
 
@@ -96,5 +94,9 @@ Distributed under the AGPL 3.0. See `LICENSE.txt` for more information.
 
 ## Acknowledgments
 
+Thanks to DigitalOcean for sponsoring the project!
+
+[![DigitalOcean Referral Badge](https://web-platforms.sfo2.cdn.digitaloceanspaces.com/WWW/Badge%201.svg)](https://www.digitalocean.com/?refcode=4edf05429dca&utm_campaign=Referral_Invite&utm_medium=Referral_Program&utm_source=badge)
+
 * [Thanks to Pawel Czerwinski for the image on the login screen](https://unsplash.com/@pawel_czerwinski)
 

Writerside/Writerside_libraries.tree

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE instance-profile
-        SYSTEM "https://resources.jetbrains.com/writerside/1.0/product-profile.dtd">
-
-<instance-profile id="Writerside_libraries"
-                  name="Writerside_libraries" is-library="true" start-page="notes.topic">
-
-    <toc-element topic="notes.topic"/>
-</instance-profile>

Writerside/c.list

@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE categories
-        SYSTEM "https://resources.jetbrains.com/writerside/1.0/categories.dtd">
-<categories>
-    <category id="wrs" name="Writerside documentation" order="1"/>
-</categories>

Writerside/cfg/buildprofiles.xml

@@ -1,34 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE buildprofiles SYSTEM "https://resources.jetbrains.com/writerside/1.0/build-profiles.dtd">
-<buildprofiles xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-               xsi:noNamespaceSchemaLocation="https://resources.jetbrains.com/writerside/1.0/build-profiles.xsd">
-    <sitemap priority="0.35" change-frequency="monthly"/>
-    <variables>
-    </variables>
-    <build-profile instance="mm">
-        <variables>
-            <noindex-content>false</noindex-content>
-            <custom-favicons>favicon.ico</custom-favicons>
-            <header-logo>logo.svg</header-logo>
-
-            <download-title>Get MediaManager</download-title>
-            <download-page>https://maxdorninger.github.io/MediaManager/configuration-overview.html</download-page>
-            <showDownloadButton>true</showDownloadButton>
-            <product-web-url>https://github.com/maxdorninger/MediaManager</product-web-url>
-
-            <algolia-id>5SXJTW5J6S</algolia-id>
-            <algolia-api-key>ed89153df615ded46c214c9390539f3b</algolia-api-key>
-            <algolia-show-logo>true</algolia-show-logo>
-            <algolia-index>MediaManagerDocs</algolia-index>
-        </variables>
-        <footer>
-            <copyright>Maximilian Dorninger 2025</copyright>
-            <social type="github" href="https://github.com/maxdorninger/MediaManager" />
-            <social type="reddit" href="https://www.reddit.com/r/MediaManager/" />
-            <link href="https://github.com/maxdorninger/MediaManager/issues">Report an Issue</link>
-            <link href="https://github.com/maxdorninger">Maximilian Dorninger</link>
-            <link href="https://github.com/sponsors/maxdorninger">Donate</link>
-        </footer>
-    </build-profile>
-
-</buildprofiles>

Writerside/mm.tree

@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE instance-profile
-        SYSTEM "https://resources.jetbrains.com/writerside/1.0/product-profile.dtd">
-
-<instance-profile id="mm"
-                  name="MediaManager" start-page="Introduction.topic">
-
-    <toc-element topic="Introduction.topic"/>
-    <toc-element topic="configuration-overview.md"/>
-    <toc-element topic="User-Guide.md">
-        <toc-element topic="Importing-existing-media.md"/>
-    </toc-element>
-    <toc-element topic="Configuration.md">
-        <toc-element topic="configuration-backend.md"/>
-        <toc-element topic="authentication-setup.md"/>
-        <toc-element topic="database-configuration.md"/>
-        <toc-element topic="download-client-configuration.md"/>
-        <toc-element topic="Indexer-Settings.md"/>
-        <toc-element topic="Scoring-Rulesets.md"/>
-        <toc-element topic="Notifications.md"/>
-        <toc-element topic="Custom-Libraries.md"/>
-        <toc-element topic="Logging.md"/>
-    </toc-element>
-    <toc-element topic="Advanced-Features.md">
-        <toc-element topic="qBittorrent-Category.md"/>
-        <toc-element topic="url-prefix.md"/>
-        <toc-element topic="metadata-provider-configuration.md"/>
-        <toc-element topic="Custom-port.md"/>
-        <toc-element topic="Follow-symlinks-in-frontend-files.md"/>
-    </toc-element>
-    <toc-element topic="troubleshooting.md"/>
-    <toc-element topic="developer-guide.md"/>
-    <toc-element topic="api-reference.md"/>
-    <toc-element topic="Screenshots.md"/>
-</instance-profile>

Writerside/redirection-rules.xml

@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE rules SYSTEM "https://resources.jetbrains.com/writerside/1.0/redirection-rules.dtd">
-<rules>
-    <!-- format is as follows
-    <rule id="<unique id>">
-        <accepts>page.html</accepts>
-    </rule>
-    -->
-    <rule id="63c34f28">
-        <description>Created after removal of "Installation" from MediaManager</description>
-        <accepts>installation.html</accepts>
-    </rule>
-    <rule id="440cb672">
-        <description>Created after removal of "About MediaManager" from MediaManager</description>
-        <accepts>starter-topic.html</accepts>
-    </rule>
-    <rule id="666c8c31">
-        <description>Created after removal of "User Guide" from MediaManager</description>
-        <accepts>user-guide.html</accepts>
-    </rule>
-    <rule id="6822e619">
-        <description>Created after removal of "Quick Start Guide" from MediaManager</description>
-        <accepts>Quick-Start-Guide.html</accepts>
-    </rule>
-    <rule id="570cb9d1">
-        <description>Created after removal of "user-guide" from MediaManager</description>
-        <accepts>user-guide.html</accepts>
-    </rule>
-    <rule id="7cb7d801">
-        <description>Created after removal of "MetadataRelay" from MediaManager</description>
-        <accepts>MetadataRelay.html</accepts>
-    </rule>
-    <rule id="52a1fe89">
-        <description>Created after removal of "Frontend" from MediaManager</description>
-        <accepts>configuration-frontend.html</accepts>
-    </rule>
-    <rule id="6242074">
-        <description>Created after removal of "Reverse Proxy" from MediaManager</description>
-        <accepts>Reverse-Proxy.html</accepts>
-    </rule>
-    <rule id="7683f141">
-        <description>Created after removal of "Other Settings" from MediaManager</description>
-        <accepts>Other-Settings.html</accepts>
-    </rule>
-</rules>

Writerside/topics/Advanced-Features.md

@@ -1,4 +0,0 @@
-# Advanced Features
-
-The features in this section are not required to run MediaManager and serve their purpose in very specific environments,
-but they can enhance your experience and provide additional functionality.

Writerside/topics/Configuration.md

@@ -1,75 +0,0 @@
-# Configuration
-
-MediaManager uses a TOML configuration file (`config.toml`) for all backend settings.
-This centralized configuration approach makes it easier to manage, backup, and share your MediaManager setup.
-
-Frontend settings are configured through environment variables in your `docker-compose.yaml` file.
-
-## Configuration File Location
-
-<warning>Note that MediaManager may need to be restarted for changes in the config file to take effect.</warning>
-
-Your `config.toml` file should be in the directory that's mounted to `/app/config/config.toml` inside the container:
-
-```yaml
-volumes:
-  - ./config:/app/config
-```
-
-Though you can change the location of the configuration file's directory by setting the `CONFIG_DIR` env variable to
-another path,
-e.g. `/etc/mediamanager/`.
-
-## Configuration Sections
-
-The configuration is organized into the following sections:
-
-- `[misc]` - General settings
-- `[database]` - Database settings
-- `[auth]` - Authentication settings
-- `[notifications]` - Notification settings (Email, Gotify, Ntfy, Pushover)
-- `[torrents]` - Download client settings (qBittorrent, Transmission, SABnzbd)
-- `[indexers]` - Indexer settings (Prowlarr and Jackett )
-- `[metadata]` - TMDB and TVDB settings
-
-## Configuring Secrets
-
-For sensitive information like API keys, passwords, and secrets, you _should_ use environment variables.
-You can actually set every configuration value through environment variables.
-For example, to set the `token_secret` value for authentication, with a .toml file you would use:
-
-```toml
-[auth]
-token_secret = "your_super_secret_key_here"
-```
-
-But you can also set it through an environment variable:
-
-```
-MEDIAMANAGER_AUTH__TOKEN_SECRET = "your_super_secret_key_here"
-```
-
-or another example with the OIDC client secret:
-
-```toml
-[auth]
-...
-[auth.openid_connect]
-client_secret = "your_client_secret_from_provider"
-```
-
-env variable:
-
-```
-MEDIAMANAGER_AUTH__OPENID_CONNECT__CLIENT_SECRET = "your_client_secret_from_provider"
-```
-
-So for every config "level", you basically have to take the name of the value and prepend it with the section names in
-uppercase with 2 underscores as delimiters and `MEDIAMANAGER_` as the prefix.
-
-<warning>Note that not every env variable starts with <code>MEDIAMANAGER_</code>,
-this prefix only applies to env variables which replace/overwrite values in the config file.
-Variables like the <code>CONFIG_DIR</code> env variable must not be prefixed.
-</warning>
-
-

Writerside/topics/Custom-port.md

@@ -1,4 +0,0 @@
-# Custom port
-
-With the env variable `PORT`, you can change the port that MediaManager listens on. The default port is `8000`.
-Note that this setting only works if you are using the Docker Image.

Writerside/topics/Follow-symlinks-in-frontend-files.md

@@ -1,6 +0,0 @@
-# Follow symlinks in frontend files
-
-MediaManager can be configured to follow symlinks when serving frontend files. This is useful if you have a setup where
-your frontend files are stored in a different location, and you want to symlink them into the MediaManager frontend directory.
-
-To enable this feature, set the `FRONTEND_FOLLOW_SYMLINKS` environment variable to `true`.

Writerside/topics/Importing-existing-media.md

@@ -1,78 +0,0 @@
-# Importing existing media
-
-In order for MediaManager to be able to import existing media (e.g. downloaded by Sonarr or Radarr)
-2 conditions have to be met:
-
-1. The folder's name must not start with a dot.
-2. The media must be in the root tv/movie library
-
-Here is an example, using these rules:
-
-```
-/
-└── data/
-    ├── tv/
-    │   ├── Rick and Morty # WILL be imported
-    │   ├── Stranger Things (2016) {tvdb_12345} [x265] # WILL be imported
-    │   ├── Breaking Bad (2008) [tmdbid-1396] # WILL be imported
-    │   ├── .The Office (2013) # WILL NOT
-    │   │
-    │   └── my-custom-library/
-    │       └── The Simpsons # WILL NOT be imported
-    └── movie/
-        └── Oppenheimer (2023) # WILL be imported
-```
-
-Is your folder structure in the correct format, you can start importing. For this,
-you just need to login as an administrator and go to the TV/movie dashboard.
-
-<note>
-When importing, no files will be deleted, moved or copied! Instead, they will be hard linked.
-</note>
-
-After importing, MediaManager will automatically prefix the old root TV show/movie folders with a dot,
-in order to mark them as 'imported'.
-
-So after importing, the directory would look like this (using the above directory structure):
-
-```
-/
-└── data/
-    ├── tv/
-    │   ├── .Rick and Morty # RENAMED
-    │   ├── Rick and Morty (2013) [tmdbid-60625] # IMPORTED
-    │   │
-    │   ├── .Stranger Things (2016) {tvdb_12345} [x265]
-    │   ├── Stranger Things (2016) [tmdbid-66732] # IMPORTED
-    │   │
-    │   ├── .The Office (2013) # IGNORED
-    │   │
-    │   ├── .Breaking Bad (2008) [tmdbid-1396]
-    │   ├── Breaking Bad (2008) [tmdbid-1396] # IMPORTED
-    │   │
-    │   └── my-custom-library/
-    │       └── The Simpsons # IGNORED
-    └── movie/
-        ├── .Oppenheimer (2023)
-        └── Oppenheimer (2023) [tmdbid-872585] # IMPORTED
-```
-
-## More criteria for importing
-
-These are the criteria specifically for the files themselves:
-
-- movie folders (e.g. `Oppenheimer (2023)`) must not contain more or less than one video file (an .mp4 or .mkv, etc.
-  file)
-- the specific structure of season folders or episode folders or naming of them does not matter
-- Episode files (video and subtitle files) must contain the season and episode number in their name, e.g. `S01E01.mp4`
-  or `S03E07 Rick and Morty.mkv`
-
-<tip>
-In any usual Sonarr/Radarr setup these file criteria should already be met by default.
-</tip>
-
-## Miscellaneous information
-
-- make MediaManager ignore directories by prefixing them with a dot
-- after importing, especially TV shows, manually check if all files are in the right place
-- MediaManager outputs in the logs if an episode/movie could not be imported

Writerside/topics/Indexer-Settings.md

@@ -1,74 +0,0 @@
-# Indexers
-
-Indexer settings are configured in the `[indexers]` section of your `config.toml` file. MediaManager supports both
-Prowlarr and Jackett as indexer providers.
-
-## Prowlarr (`[indexers.prowlarr]`)
-
-- `enabled`
-
-Set to `true` to enable Prowlarr. Default is `false`.
-
-- `url`
-
-Base URL of your Prowlarr instance.
-
-- `api_key`
-
-API key for Prowlarr. You can find this in Prowlarr's settings under General.
-
-- `timeout_seconds`
-
-Timeout in seconds for requests to Prowlarr. Default is `60` seconds.
-Symptoms of timeouts are typically no search results (*"No torrents found!"*) in conjunction with logs like these:
-
-```
-DEBUG - media_manager.indexer.utils -
- follow_redirects_to_final_torrent_url():
-  An error occurred during the request for <some-url>:
-   HTTPConnectionPool(host='<some-host>', port=<some-port>):
-    Read timed out. (read timeout=10)
-```
-
-## Jackett (`[indexers.jackett]`)
-
-- `enabled`
-
-Set to `true` to enable Jackett. Default is `false`.
-
-- `url`
-
-Base URL of your Jackett instance.
-
-- `api_key`
-
-API key for Jackett. You can find this in Jackett's dashboard.
-
-- `indexers`
-
-List of indexer names to use with Jackett. You can specify which indexers Jackett should search through.
-
-- `timeout_seconds`
-
-Refer to the Prowlarr section for details.
-
-## Example Configuration
-
-Here's a complete example of the indexers section in your `config.toml`:
-
-```toml
-[indexers]
-[indexers.prowlarr]
-enabled = true
-url = "http://prowlarr:9696"
-api_key = "your_prowlarr_api_key"
-timeout_seconds = 60
-
-[indexers.jackett]
-enabled = false
-url = "http://jackett:9117"
-api_key = "your_jackett_api_key"
-indexers = ["1337x", "rarbg"]
-timeout_seconds = 60
-
-```

Writerside/topics/Introduction.topic

@@ -1,74 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE topic
-        SYSTEM "https://resources.jetbrains.com/writerside/1.0/xhtml-entities.dtd">
-<topic xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-       xsi:noNamespaceSchemaLocation="https://resources.jetbrains.com/writerside/1.0/topic.v2.xsd"
-       title="Introduction" id="Introduction">
-    <section-starting-page>
-        <title>MediaManager</title>
-        <description>
-            MediaManager is modern software to manage your TV and movie library. It is designed to be a replacement for Sonarr,
-            Radarr, Overseer, Unpackerr and Jellyseer.
-            It supports TVDB and TMDB for metadata, supports OIDC and OAuth 2.0 for authentication and supports Prowlarr and
-            Jackett.
-        </description>
-        <spotlight>
-            <card href="configuration-overview.md" badge="start"
-                  summary="Installation Guide"/>
-            <card href="Configuration.md" badge="settings"
-                  summary="Configuration Overview"/>
-        </spotlight>
-        <primary>
-            <title>Other Topics</title>
-            <card href="developer-guide.md" badge="development"
-                  summary="Developer Guide"/>
-            <card href="troubleshooting.md" badge="support"
-                  summary="Troubleshooting Guide"/>
-            <card href="Advanced-Features.md"
-                  summary="Advanced Features"/>
-            <card href="Screenshots.md"
-                  summary="Screenshots"/>
-        </primary>
-        <secondary>
-            <title>Support MediaManager &amp; Maximilian Dorninger</title>
-            <card href="https://github.com/sponsors/maxdorninger"
-                  summary="Sponsor me on Github Sponsors :)"/>
-            <card href="https://buymeacoffee.com/maxdorninger"
-                  summary="Buy me a coffee :)"/>
-        </secondary>
-        <misc>
-            <cards narrow="true">
-                <title>MediaManager Sponsors</title>
-                <card href="https://github.com/ldrrp"
-                      summary="ldrrp" image="https://github.com/ldrrp.png" />
-                <card href="https://fosstodon.org/@aljazmerzen"
-                      summary="aljamerzen" image="https://cdn.fosstodon.org/accounts/avatars/107/626/197/378/907/137/original/e93602705171fd0a.jpg"/>
-                <card href="https://github.com/SeimusS"
-                      summary="SeimusS" image="https://github.com/SeimusS.png" />
-                <card href="https://github.com/HadrienKerlero"
-                      summary="HadrienKerlero" image="https://github.com/HadrienKerlero.png" />
-                <card href="https://github.com/brandon-dacrib"
-                      summary="brandon-dacrib" image="https://github.com/brandon-dacrib.png" />
-                <card href="https://github.com/keyxmakerx"
-                      summary="keyxmakerx" image="https://github.com/keyxmakerx.png" />
-                <card href="https://github.com/LITUATUI"
-                      summary="LITUATUI" image="https://github.com/LITUATUI.png" />
-                <card href="https://buymeacoffee.com/maxdorninger"
-                      summary="Nicolas" image="https://cdn.buymeacoffee.com/uploads/profile_pictures/default/v2/B6CDBD/NI.png" />
-                <card href="https://buymeacoffee.com/maxdorninger"
-                      summary="Josh" image="https://cdn.buymeacoffee.com/uploads/profile_pictures/default/v2/DEBBB9/JO.png" />
-                <card href="https://buymeacoffee.com/maxdorninger"
-                      summary="PuppiestDoggo" image="https://cdn.buymeacoffee.com/uploads/profile_pictures/2025/11/2VeQ8sTGPhj4tiLy.jpg" />
-                <card href="https://github.com/seferino-fernandez"
-                      summary="Seferino" image="https://avatars.githubusercontent.com/u/5546622" />
-            </cards>
-            <links>
-                <group>
-                    <title>MediaManager Repository</title>
-                    <a href="https://github.com/maxdorninger/MediaManager"
-                          summary="MediaManager Repository"/>
-                </group>
-            </links>
-        </misc>
-    </section-starting-page>
-</topic>

Writerside/topics/Logging.md

@@ -1,17 +0,0 @@
-# Logging
-
-MediaManager automatically logs events and errors to help with troubleshooting and monitoring. These logs are emitted to
-the console (stdout) by default, and to a json-formatted log file.
-
-## Configuring Logging
-
-The location of the log file can be configured with the `LOG_FILE` environment variable. By default, the log file is
-located at
-`/app/config/media_manager.log`. When changing the log file location, ensure that the directory exists, is writable by the
-MediaManager container and that it is a full path.
-
-With the `MEDIAMANAGER_LOG_LEVEL` environment variable, you can set the logging level. The available levels are:
-- `DEBUG` - Detailed information, typically of interest only when diagnosing problems.
-- `INFO` - The default level, for general operational entries about what's going on inside the application.
-- `WARNING`
-- `ERROR`

Writerside/topics/Scoring-Rulesets.md

@@ -1,141 +0,0 @@
-# Scoring Rulesets
-
-Scoring rulesets in MediaManager allow you to flexibly control which releases are preferred or avoided when searching
-for media. Each ruleset is a collection of scoring rules that can be assigned to one or more libraries. When
-MediaManager evaluates releases, it applies the relevant ruleset(s) to adjust the score of each result, influencing
-which releases are selected for download.
-
-## How Rulesets Work
-
-- **Rulesets** are defined in the configuration and contain a list of rule names and the libraries they apply to.
-- **Scoring rules** can target keywords in release titles or specific indexer flags.
-- When searching for a release, MediaManager checks which library the media belongs to and applies the corresponding
-  ruleset.
-
-## Rules
-
-Rules define how MediaManager scores releases based on their titles or indexer flags. You can create rules that:
-
-- Prefer releases with specific codecs (e.g., H.265 over H.264).
-- Avoid releases with certain keywords (e.g., "CAM", "TS", "Nuked").
-- Reject releases that do not meet certain criteria (e.g., non-freeleech releases).
-- and more.
-
-<note>
-The keywords and flags are compared case-insensitively.
-</note>
-
-### Title Rules
-
-Title rules allow you to adjust the score of a release based on the presence (or absence) of specific keywords in the release title. This is useful for preferring or avoiding certain encodings, sources, or other characteristics that are typically included in release names.
-
-Each title rule consists of:
-- `name`: A unique identifier for the rule.
-- `keywords`: A list of keywords to search for in the release title.
-- `score_modifier`: The amount to add or subtract from the score if a keyword matches.
-- `negate`: If true, the rule applies when none of the keywords are present.
-
-#### Examples for Title Rules
-
-```toml
-[[indexers.title_scoring_rules]]
-name = "prefer_h265"
-keywords = ["h265", "hevc", "x265"]
-score_modifier = 100
-negate = false
-
-[[indexers.title_scoring_rules]]
-name = "avoid_cam"
-keywords = ["cam", "ts"]
-score_modifier = -10000
-negate = false
-```
-
-- The first rule increases the score for releases containing "h265", "hevc", or "x265".
-- The second rule heavily penalizes releases containing "cam" or "ts".
-
-If `negate` is set to `true`, the `score_modifier` is applied only if none of the keywords are found in the title.
-
-### Indexer Flag Rules
-
-Indexer flag rules adjust the score based on flags provided by the indexer (such as `freeleech`, `nuked`, etc). These flags are often used to indicate special properties or warnings about a release.
-
-Each indexer flag rule consists of:
-- `name`: A unique identifier for the rule.
-- `flags`: A list of indexer flags to match.
-- `score_modifier`: The amount to add or subtract from the score if a flag matches.
-- `negate`: If true, the rule applies when none of the flags are present.
-
-#### Examples for Indexer Flag Rules
-
-```toml
-[[indexers.indexer_flag_scoring_rules]]
-name = "reject_non_freeleech"
-flags = ["freeleech", "freeleech75"]
-score_modifier = -10000
-negate = true
-
-[[indexers.indexer_flag_scoring_rules]]
-name = "reject_nuked"
-flags = ["nuked"]
-score_modifier = -10000
-negate = false
-```
-
-- The first rule penalizes releases that do **not** have the "freeleech" or "freeleech75" flag.
-- The second rule penalizes releases that are marked as "nuked".
-
-If `negate` is set to `true`, the `score_modifier` is applied only if none of the flags are present on the release.
-
-## Example
-
-```toml
-[[indexers.scoring_rule_sets]]
-name = "default"
-libraries = ["ALL_TV", "ALL_MOVIES"]
-rule_names = ["prefer_h265", "avoid_cam", "reject_nuked"]
-
-[[indexers.scoring_rule_sets]]
-name = "strict_quality"
-libraries = ["ALL_MOVIES"]
-rule_names = ["prefer_h265", "avoid_cam", "reject_non_freeleech"]
-```
-
-
-
-## Libraries
-
-The libraries that are mentioned in the preceding example are explained in greater detail in
-the [Library config section](Custom-Libraries.md).
-
-### Special Libraries
-
-You can use special library names in your rulesets:
-
-- `ALL_TV`: Applies the ruleset to all TV libraries.
-- `ALL_MOVIES`: Applies the ruleset to all movie libraries.
-- `Default`: Applies the ruleset to all media that is not part of a custom library.
-
-This allows you to set global rules for all TV or movie content, or provide fallback rules for uncategorized media.
-
-<tip>
-
-You don't need to create lots of libraries with different directories, multiple libraries can share the same directory.
-You can set multiple (unlimited) libraries to the default directory `/data/movies` or `/data/tv` and use different
-rulesets with them.
-
-</tip>
-
-
-
-## Relation to Sonarr/Radarr Profiles
-
-MediaManager's scoring rules and rulesets system is an alternative to Sonarr's Quality, Custom, and Release Profiles. I
-designed this system with the goal of being more intuitive and flexible, since I noticed that a lot of people are
-overwhelmed by Sonarrs/Radarrs system.
-
-- **Quality Profiles**: Use scoring rules to prefer or avoid certain codecs, resolutions, or other quality indicators.
-- **Custom/Release Profiles**: Use title or flag-based rules to match or exclude releases based on keywords or indexer
-  flags.
-
-This approach provides a powerful and transparent way to fine-tune your automation.

Writerside/topics/Screenshots.md

@@ -1,17 +0,0 @@
-# Screenshots
-
-<note> MediaManager also supports darkmode!</note>
-
-![screenshot-dashboard.png](screenshot-dashboard.png)
-
-![screenshot-tv-dashboard.png](screenshot-tv-dashboard.png)
-
-![screenshot-download-season.png](screenshot-download-season.png)
-
-![screenshot-request-season.png](screenshot-request-season.png)
-
-![screenshot-tv-torrents.png](screenshot-tv-torrents.png)
-
-![screenshot-settings.png](screenshot-settings.png)
-
-![screenshot-login.png](screenshot-login.png)

Writerside/topics/User-Guide.md

@@ -1,51 +0,0 @@
-# Usage
-
-If you are coming from Radarr or Sonarr you will find that MediaManager does things a bit differently.
-Instead of completely automatically downloading and managing your media, MediaManager focuses on providing an
-easy-to-use interface to guide you through the process of finding and downloading media. Advanced features like multiple
-qualities of a show/movie necessitate such a paradigm shift.
-__So here is a quick step-by-step guide to get you started:__
-
-<tabs>
-    <tab id="as-a-user" title="as a user">
-        <procedure title="Downloading/Requesting a show" id="request-show-user">
-           <step>Add a show on the "Add Show" page</step>
-           <step>After adding the show you will be redirected to the show's page.</step>
-           <step>There you can click the "Request Season" button.</step>
-           <step>Select one or more seasons that you want to download</step>
-           <step>Then select the "Min Quality", this will be the minimum resolution of the content to download.</step>
-           <step>Then select the "Wanted Quality", this will be the <strong>maximum</strong> resolution of the content to download.</step>
-           <step>Finally click Submit request, though this is not the last step!</step>
-           <step>An administrator first has to approve your request for download, only then will the requested content be downloaded.</step>
-           <p>Congratulation! You've downloaded a show.</p>
-        </procedure>
-    </tab>
-    <tab id="as-an-admin" title="as an admin">
-        <procedure title="Requesting a show" id="request-show-admin">
-           <step>Add a show on the "Add Show" page</step>
-           <step>After adding the show you will be redirected to the show's page.</step>
-           <step>There you can click the "Request Season" button.</step>
-           <step>Select one or more seasons that you want to download</step>
-           <step>Then select the "Min Quality", this will be the minimum resolution of the content to download.</step>
-           <step>Then select the "Wanted Quality", this will be the <strong>maximum</strong> resolution of the content to download.</step>
-           <step>Finally click Submit request, as you are an admin, your request will be automatically approved.</step>
-           <p>Congratulation! You've downloaded a show.</p>
-        </procedure>
-        <procedure title="Downloading a show" id="download-show-admin">
-            <p>You can only directly download a show if you are an admin!</p>
-           <step>Go to a show's page.</step>
-           <step>There you can click the "Download Season" button.</step>
-           <step>Enter the season's number that you want to download</step>
-           <step>Then optionally select the "File Path Suffix", <strong>it needs to be unique per season per show!</strong> </step>
-           <step>Then click "Download" on a torrent that you want to download.</step>
-           <p>Congratulation! You've downloaded a show.</p>
-        </procedure>
-        <procedure title="Managing requests" id="approving-request-admin">
-           <p>Users need their requests to be approved by an admin, to do this follow these steps:</p>
-           <step>Go to the "Requests" page.</step>
-           <step>There you can approve, delete or modify a user's request.</step>
-        </procedure>
-    </tab>
-</tabs>
-
-

Writerside/topics/api-reference.md

@@ -1,8 +0,0 @@
-# API Reference
-
-Media Manager's backend is built with FastAPI, which automatically generates interactive API documentation.
-
-* **Swagger UI**  (typically available at `http://localhost:8000/docs`).
-* **ReDoc** (typically available at `http://localhost:8000/redoc`).
-
-

Writerside/topics/authentication-setup.md

@@ -1,95 +0,0 @@
-# Authentication
-
-MediaManager supports multiple authentication methods. Email/password authentication is the default, but you can also
-enable OpenID Connect (OAuth 2.0) for integration with external identity providers.
-
-All authentication settings are configured in the `[auth]` section of your `config.toml` file.
-
-## General Authentication Settings (`[auth]`)
-
-- `token_secret`
-
-Strong secret key for signing JWTs (create with `openssl rand -hex 32`). This is a required field.
-
-- `session_lifetime`
-
-Lifetime of user sessions in seconds. Default is `86400` (1 day).
-
-- `admin_emails`
-
-A list of email addresses for administrator accounts. This is a required field.
-
-- `email_password_resets`
-
-Toggle for enabling password resets via email. If users request a password reset because they forgot their password,
-they will be sent an email with a link to reset it. Default is `false`.
-
-<note>
-    To use email password resets, you must also configure SMTP settings in the <code>[notifications.smtp_config]</code> section.
-</note>
-
-<include from="notes.topic" element-id="auth-admin-emails"></include>
-
-## OpenID Connect Settings (`[auth.openid_connect]`)
-
-OpenID Connect allows you to integrate with external identity providers like Google, Microsoft Azure AD, Keycloak, or
-any other OIDC-compliant provider.
-
-- `enabled`
-
-Set to `true` to enable OpenID Connect authentication. Default is `false`.
-
-- `client_id`
-
-Client ID provided by your OpenID Connect provider.
-
-- `client_secret`
-
-Client secret provided by your OpenID Connect provider.
-
-- `configuration_endpoint`
-
-OpenID Connect configuration endpoint URL. Note the lack of a trailing slash - this is important. It usually ends with
-`.well-known/openid-configuration`.
-
-- `name`
-
-Display name for the OpenID Connect provider that will be shown on the login page.
-
-### Configuration for your OpenID Connect Provider
-
-#### Redirect URI
-
-The OpenID server will likely require a redirect URI. This URL will usually look something like this:
-
-```
-{MEDIAMANAGER_URL}/api/v1/auth/oauth/callback
-```
-
-<warning>It is very important that you set the correct callback URI, otherwise it won't work!</warning>
-
-#### Authentik Example {collapsible="true"}
-
-Here is an example configuration for the OpenID Connect provider for Authentik.
-
-![authentik-redirect-url-example](authentik-redirect-url-example.png)
-
-
-## Example Configuration
-
-Here's a complete example of the authentication section in your `config.toml`:
-
-```toml
-[auth]
-token_secret = "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6"
-session_lifetime = 604800  # 1 week
-admin_emails = ["admin@example.com", "manager@example.com"]
-email_password_resets = true
-
-[auth.openid_connect]
-enabled = true
-client_id = "mediamanager-client"
-client_secret = "your-secret-key-here"
-configuration_endpoint = "https://auth.example.com/.well-known/openid-configuration"
-name = "Authentik"
-```

Writerside/topics/configuration-backend.md

@@ -1,48 +0,0 @@
-# Backend
-
-These settings configure the core backend application through the `config.toml` file. All backend configuration is now
-centralized in this TOML file instead of environment variables.
-
-## General Settings (`[misc]`)
-
-- `frontend_url`
-
-The URL the frontend will be accessed from. This is a required field and must not include a trailing slash. The default
-path is `http://localhost:8000`.
-
-E.g. if you are accessing MediaManager at `http://example.com/media` where `/media` is the base path, set this to: `http://example.com/media`.
-
-If you are accessing MediaManager at the root of a domain, e.g. `https://mediamanager.example.com`, set this to `https://mediamanager.example.com`.
-
-Make sure to change this to the URL you will use to access the application in your browser.
-
-<tip>
-    Note that this doesn't affect where the server binds, nor does it affect the base URL prefix. See the page on <a href="url-prefix.md"><code>BASE_PATH</code></a> for information on how to configure a prefix.
-</tip>
-
-- `cors_urls`
-
-A list of origins you are going to access the API from. Note the lack of trailing slashes.
-
-- `development`
-
-Set to `true` to enable development mode. Default is `false`.
-
-## Example Configuration
-
-Here's a complete example of the general settings section in your `config.toml`:
-
-```toml
-[misc]
-# REQUIRED: Change this to match your actual frontend domain.
-frontend_url = "http://mediamanager.dev"
-
-cors_urls = ["http://localhost:8000"]
-
-# Optional: Development mode (set to true for debugging)
-development = false
-```
-
-<note>
-    The <code>frontend_url</code> is the most important settings to configure correctly. Make sure it matches your actual deployment URLs.
-</note>

Writerside/topics/configuration-overview.md

@@ -1,33 +0,0 @@
-# Installation Guide
-
-The recommended way to install and run Media Manager is using Docker and Docker Compose.
-
-## Prerequisites
-
-* Ensure Docker and Docker Compose are installed on your system.
-* If you plan to use OAuth 2.0 / OpenID Connect for authentication, you will need an account and client credentials
-  from an OpenID provider (e.g., Authentik, Pocket ID).
-
-## Setup
-
-* Download the `docker-compose.yaml` from the MediaManager repo with the following command:
-  ```bash
-  wget -O docker-compose.yaml https://raw.githubusercontent.com/maxdorninger/MediaManager/refs/heads/master/docker-compose.yaml
-  mkdir config
-  wget -O ./config/config.toml https://raw.githubusercontent.com/maxdorninger/MediaManager/refs/heads/master/config.example.toml
-  # you probably need to edit the config.toml file in the ./config directory, for more help see the documentation
-  docker compose up -d
-  ```
-
-* Upon first run, MediaManager will create a default `config.toml` file in the `./config` directory.
-
-* You can edit this file to configure MediaManager according to your needs.
-
-* Upon first run, MediaManager will also create a default admin user with the email, it's recommended to change the
-  password of this user after the first login. The credentials of the default admin user will be printed in the logs of
-  the container.
-
-* For more information on the available configuration options, see the [Configuration section](Configuration.md) of the
-  documentation.
-
-<include from="notes.topic" element-id="auth-admin-emails"></include>

Writerside/topics/contributing.md

@@ -1 +0,0 @@
-# Contributing

Writerside/topics/database-configuration.md

@@ -1,42 +0,0 @@
-# Database
-
-Database settings are configured in the `[database]` section of your `config.toml` file. MediaManager uses PostgreSQL as its database backend.
-
-## Database Settings (`[database]`)
-
-- `host`
-
-Hostname or IP of the PostgreSQL server. Default is `localhost`.
-
-- `port`
-
-Port number of the PostgreSQL server. Default is `5432`.
-
-- `user`
-
-Username for PostgreSQL connection. Default is `MediaManager`.
-
-- `password`
-
-Password for the PostgreSQL user. Default is `MediaManager`.
-
-- `dbname`
-
-Name of the PostgreSQL database. Default is `MediaManager`.
-
-## Example Configuration
-
-Here's a complete example of the database section in your `config.toml`:
-
-```toml
-[database]
-host = "db"
-port = 5432
-user = "MediaManager"
-password = "your_secure_password"
-dbname = "MediaManager"
-```
-
-<tip>
-    In docker-compose deployments the containers name is simultaneously its hostname, so you can use "db" or "postgres" as host.
-</tip>

Writerside/topics/developer-guide.md

@@ -1,349 +0,0 @@
-# Developer Guide
-
-This section is for those who want to contribute to Media Manager or understand its internals.
-
-## Source Code directory structure
-
-- `media_manager/`: Backend FastAPI application
-- `web/`: Frontend SvelteKit application
-- `Writerside/`: Documentation
-- `metadata_relay/`: Metadata relay service, also FastAPI
-
-## Special Dev Configuration
-
-### Environment Variables
-
-MediaManager uses various environment variables for configuration. In the Docker development setup (
-`docker-compose.dev.yaml`), most of these are automatically configured for you.
-
-#### Backend Variables
-
-- `BASE_PATH`: Sets the base path for the app (e.g., for subdirectory deployments)
-- `PUBLIC_VERSION`: Version string displayed in `/api/v1/health` endpoint
-- `FRONTEND_FILES_DIR`: Directory for built frontend files (e.g., `/app/web/build` in Docker)
-- `MEDIAMANAGER_MISC__DEVELOPMENT`: When set to `TRUE`, enables FastAPI hot-reloading in Docker
-
-#### Frontend Variables
-
-- `PUBLIC_API_URL`: API URL for backend communication (automatically configured via Vite proxy in Docker)
-- `PUBLIC_VERSION`: Version string displayed in the frontend UI
-- `BASE_PATH`: Base path for frontend routing (matches backend BASE_PATH)
-
-#### Docker Development Variables
-
-- `DISABLE_FRONTEND_MOUNT`: When `TRUE`, disables mounting built frontend files (allows separate frontend container)
-
-<tip>
-    This is automatically set in <code>docker-compose.dev.yaml</code> to enable the separate frontend development container
-</tip>
-
-#### Configuration Files
-
-- Backend: `res/config/config.toml` (created from `config.dev.toml`)
-- Frontend: `web/.env` (created from `.env.example`)
-
-## Contributing
-
-- Consider opening an issue to discuss changes before starting work
-
-## Setting up the Development Environment
-
-I use IntellijIdea with the Pycharm and Webstorm plugins to develop this, but this guide should also work with VSCode.
-Normally I'd recommend Intellij, but unfortunately only Intellij Ultimate has support for FastAPI and some other
-features.
-
-### Recommended VSCode Plugins
-
-- Python
-- Svelte for VSCode
-- and probably more, but I don't use VSCode myself, so I can't recommend anymore.
-
-### Recommended Intellij/Pycharm Plugins
-
-- Python
-- Svelte
-- Pydantic
-- Ruff
-- VirtualKit
-- Writerside (for writing documentation)
-
-### Recommended Development Workflow
-
-The **recommended way** to develop MediaManager is using the fully Dockerized setup with `docker-compose.dev.yaml`.
-This ensures you're working in the same environment as production and makes it easy for new contributors to get started
-without installing Python, Node.js, or other dependencies locally.
-
-The development environment includes:
-
-- **Backend (FastAPI)** with automatic hot-reloading for Python code changes
-- **Frontend (SvelteKit/Vite)** with Hot Module Replacement (HMR) for instant updates
-- **Database (PostgreSQL)** pre-configured and ready to use
-
-#### What supports hot reloading and what does not
-
-- Python code changes (.py files), Frontend code changes (.svelte, .ts, .css) and configuration changes (config.toml)
-  reload automatically.
-- Changing the backend dependencies (pyproject.toml) requires rebuilding:
-  `docker compose -f docker-compose.dev.yaml build mediamanager`
-- Changing the frontend dependencies (package.json) requires restarting the frontend container:
-  `docker compose -f docker-compose.dev.yaml restart frontend`
-- Database migrations: Automatically run on backend container startup
-
-This approach eliminates the need for container restarts during normal development and provides the best developer
-experience with instant feedback for code changes.
-
-#### How the Frontend Connects to the Backend
-
-In the Docker development setup, the frontend and backend communicate through Vite's proxy configuration:
-
-- **Frontend runs on**: `http://localhost:5173` (exposed from Docker)
-- **Backend runs on**: `http://mediamanager:8000` (Docker internal network)
-- **Vite proxy**: Automatically forwards all `/api/*` requests from frontend to backend
-
-This means when your browser makes a request to `http://localhost:5173/api/v1/tv/shows`, Vite automatically proxies it
-to `http://mediamanager:8000/api/v1/tv/shows`. The `PUBLIC_API_URL` environment variable is set to use this proxy, so
-you don't need to configure anything manually.
-
-### Setting up the full development environment with Docker (Recommended)
-
-This is the easiest and recommended way to get started. Everything runs in Docker with hot-reloading enabled.
-
-1. Copy the example config & .env:
-
-   ```bash
-   mkdir -p res/config # Only needed on first run
-   cp config.dev.toml res/config/config.toml
-   cp web/.env.example web/.env
-   ```
-
-2. Start all services:
-
-   ```bash
-   # Recommended: Use make commands for easy development
-   make up
-
-   # Alternative: Use docker compose directly (if make is not available)
-   docker compose -f docker-compose.dev.yaml up
-   ```
-
-   <tip> Run <code>make help</code> to see all available development commands including <code>make down</code>, <code>make logs</code>, <code>make app</code> (
-   shell into backend), and more.</tip>
-
-3. Access the application:
-   - Frontend (with HMR): <http://localhost:5173>
-   - Backend API: <http://localhost:8000>
-   - Database: localhost:5432
-
-The default user email is `admin@example.com` and password is `admin`, these are printed out in the logs accessible with `make logs`.
-That's it! Now you can edit code and see changes instantly:
-
-- Edit Python files → Backend auto-reloads
-- Edit Svelte/TypeScript files → Frontend HMR updates in browser
-- Edit config.toml → Changes apply immediately
-
-### Setting up the backend development environment (Local)
-
-1. Clone the repository
-2. cd into repo root
-3. [Install `uv`.](https://docs.astral.sh/uv/getting-started/installation/)
-4. run `uv --version` to verify that `uv` is installed correctly
-5. Install python if you haven't already:
-
-   ```bash
-   uv python install 3.13
-   ```
-
-6. Create a virtual environment with uv
-
-   ```bash
-   uv venv --python 3.13
-   ```
-
-7. Install dependencies:
-
-   ```bash
-   uv sync
-   ```
-
-8. run db migrations with
-
-   ```bash
-     uv run alembic upgrade head
-   ```
-
-9. run the backend with
-
-   ```bash
-   uv run fastapi run media_manager/main.py --reload --port 8000
-   ```
-
-- format code with `uv run ruff format .`
-- lint code with `uv run ruff check .`
-
-### Setting up the frontend development environment (Local, Optional)
-
-<note>
-Using the Docker setup above is recommended. This section is for those who prefer to run the frontend locally outside of Docker.
-</note>
-
-1. Clone the repository
-2. cd into repo root
-3. cd into `web` directory
-4. Install Node.js and npm if you haven't already, I
-   used [nvm-windows](https://github.com/coreybutler/nvm-windows?tab=readme-ov-file):
-
-   ```powershell
-   nvm install 24.1.0
-   nvm use 24.1.0
-   ```
-
-   I also needed to run the following command to be able to use `npm`:
-
-   ```powershell
-   Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
-   ```
-
-5. Create a `.env` file in the `web` directory:
-
-   ```bash
-   cp .env.example .env
-   ```
-
-   Update `PUBLIC_API_URL` if your backend is not at `http://localhost:8000`
-
-6. Install the dependencies with npm: `npm install`
-7. Start the frontend development server: `npm run dev`
-
-<tip>If running frontend locally, make sure to add <code>http://localhost:5173</code> to the <code>cors_urls</code> in your backend
-config file.</tip>
-
-- Format the code with `npm run format`
-- Lint the code with `npm run lint`
-
-## Troubleshooting
-
-### Common Docker Development Issues
-
-#### Port already in use errors
-
-- Check if ports 5173, 8000, or 5432 are already in use: `lsof -i :5173` (macOS/Linux) or
-  `netstat -ano | findstr :5173` (Windows)
-- Stop conflicting services or change ports in `docker-compose.dev.yaml`
-
-#### Container not showing code changes
-
-- Verify volume mounts are correct in `docker-compose.dev.yaml`
-- For backend: Ensure `./media_manager:/app/media_manager` is mounted
-- For frontend: Ensure `./web:/app` is mounted
-- On Windows: Check that file watching is enabled in Docker Desktop settings
-
-#### Frontend changes not updating
-
-- Check that the frontend container is running: `make ps` or `docker compose -f docker-compose.dev.yaml ps`
-- Verify Vite's file watching is working (should see HMR updates in browser console)
-- Try restarting the frontend container: `docker compose -f docker-compose.dev.yaml restart frontend`
-
-#### Backend changes not reloading
-
-- Verify `MEDIAMANAGER_MISC__DEVELOPMENT=TRUE` is set in `docker-compose.dev.yaml`
-- Check backend logs: `make logs ARGS="--follow mediamanager"` or
-  `docker compose -f docker-compose.dev.yaml logs -f mediamanager`
-- If dependencies changed, rebuild: `docker compose -f docker-compose.dev.yaml build mediamanager`
-
-#### Database migration issues
-
-- Migrations run automatically on container startup
-- To run manually: `make app` then `uv run alembic upgrade head`
-- To create new migration: `make app` then `uv run alembic revision --autogenerate -m "description"`
-
-#### Viewing logs
-
-- All services: `make logs`
-- Follow logs in real-time: `make logs ARGS="--follow"`
-- Specific service: `make logs ARGS="mediamanager --follow"`
-
-#### Interactive debugging
-
-- Shell into backend: `make app` (or `docker compose -f docker-compose.dev.yaml exec -it mediamanager bash`)
-- Shell into frontend: `make frontend` (or `docker compose -f docker-compose.dev.yaml exec -it frontend sh`)
-- Once inside, you can run commands like `uv run alembic upgrade head`, `npm install`, etc.
-
-#### Volume permission issues (Linux)
-
-- Docker containers may create files as root, causing permission issues, which can make the login page fail to show up.
-- Solution: `sudo chown -R $USER:$USER res/` to reclaim ownership.
-- Alternatively: Run containers with your user ID or use Docker's `user:` directive, this may fail though.
-
-#### Complete reset
-
-If all else fails, you can completely reset your development environment:
-
-```bash
-make down
-docker compose -f docker-compose.dev.yaml down -v  # Remove volumes
-docker compose -f docker-compose.dev.yaml build --no-cache  # Rebuild without cache
-make up
-```
-
-## Sequence Diagrams
-
-```mermaid
-sequenceDiagram
-    title Step-by-step: going from adding a show to importing a torrent of one of its seasons
-
-    User->>TV Router: Add a show (POST /tv/shows)
-    TV Router->>TV Service: Receive Show Request
-    TV Service->>MetadataProviderService: Get Metadata for Show
-    MetadataProviderService->>File System: Save Poster Image
-    TV Service->>Database: Store show information
-
-    User->>TV Router: Get Available Torrents for a Season (GET /tv/torrents)
-    TV Router->>TV Service: Receive Request
-    TV Service->>Indexer Service: Search for torrents
-    TV Service->>User: Returns Public Indexer Results
-
-    User->>TV Router: Download Torrent (POST /tv/torrents)
-    TV Router->>TV Service: Receive Request
-    Note over Database: This associates a season with a torrent id and the file_path_suffix
-    TV Service->>Database: Saves a SeasonFile object
-    TV Service->>Torrent Service: Download Torrent
-    Torrent Service->>File System: Save Torrentfile
-    Torrent Service->>QBittorrent: Download Torrent
-
-    Note over Scheduler: Hourly scheduler trigger
-    Scheduler->>TV Service: auto_import_all_show_torrents()
-    TV Service->>Database: Get all Shows and seasons which are associated with a torrent
-    TV Service->>Torrent Service: Update Torrent download statuses
-    Note over TV Service: if a torrent is finished downloading it will be imported
-    TV Service->>Torrent Service: get all files in the torrents directory
-    Note over Torrent Service: Extracts archives, guesses mimetype (Video/Subtitle/Other)
-    Note over TV Service: filters files based on some regex and renames them
-    TV Service->>File System: Move/Hardlink video and subtitle files
-
-    Note over User: User can now access the show in e.g. Jellyfin
-
-
-```
-
-## Tech Stack
-
-### Backend
-
-- Python
-- FastAPI
-- SQLAlchemy
-- Pydantic and Pydantic-Settings
-- Alembic
-
-### Frontend
-
-- TypeScript
-- SvelteKit
-- Tailwind CSS
-- shadcn-svelte
-- openapi-ts
-- openapi-fetch
-
-### CI/CD
-
-- GitHub Actions

Writerside/topics/metadata-provider-configuration.md

@@ -1,89 +0,0 @@
-# Metadata Provider Configuration
-
-Metadata provider settings are configured in the `[metadata]` section of your `config.toml` file. These settings control how MediaManager retrieves information about movies and TV shows.
-
-## TMDB Settings (`[metadata.tmdb]`)
-
-TMDB (The Movie Database) is the primary metadata provider for MediaManager. It provides detailed information about movies and TV shows.
-
-<tip>
-    Other software like Jellyfin use TMDB as well, so there won't be any metadata discrepancies.
-</tip>
-
-### `tmdb_relay_url`
-
-If you want to use your own TMDB relay service, set this to the URL of your own MetadataRelay. Otherwise, use the default relay.
-
-- **Default:** `https://metadata-relay.dorninger.co/tmdb`
-- **Example:** `https://your-own-relay.example.com/tmdb`
-
-### `primary_languages`
-
-If a TV show/movie's original language is in this list, metadata will be displayed and fetched in that language. Torrent searches done in Standard Mode uses the same fetched metadata, so if you use any language-specific tracker, you may enter the language here to get the desired search results.
-Otherwise, `default_language` will be used.
-
-**Format: ISO 639-1 codes (2 letters). Full list: https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes**
-
-- **Default:** `[]`
-- **Example:** `["no", "de", "es"]`
-
-### `default_language`
-
-<warning>
-    `default_language` sets the TMDB `language` paramater when searching and adding TV shows and movies. If TMDB does not find a matching translation, metadata in the <strong>original language</strong> will be fetched with no option for a fallback language. It is therefore highly advised to only use "broad" languages. For most use cases, the default setting is safest.
-</warning>
-
-**Format: ISO 639-1 codes (2 letters).**
-
-- **Default:** `en`
-
-## TVDB Settings (`[metadata.tvdb]`)
-
-<warning>
-    The TVDB might provide false metadata and doesn't support some features of MediaManager like showing overviews. Therefore, TMDB is the preferred metadata provider.
-</warning>
-
-### `tvdb_relay_url`
-
-If you want to use your own TVDB relay service, set this to the URL of your own MetadataRelay. Otherwise, use the default relay.
-
-- **Default:** `https://metadata-relay.dorninger.co/tvdb`
-- **Example:** `https://your-own-relay.example.com/tvdb`
-
-## MetadataRelay
-
-<note>
-  To use MediaManager <strong>you don't need to set up your own MetadataRelay</strong>, as the default relay hosted by the developer should be sufficient for most purposes.
-</note>
-
-The MetadataRelay is a service that provides metadata for MediaManager. It acts as a proxy for TMDB and TVDB, allowing you to use your own API keys if needed, but the default relay means you don't need to create accounts for API keys yourself.
-
-You might want to use your own relay if you want to avoid rate limits, protect your privacy, or for other reasons. If you know Sonarr's Skyhook, this is similar to that.
-
-### Where to get API keys
-
-- Get a TMDB API key from [The Movie Database](https://www.themoviedb.org/settings/api)
-- Get a TVDB API key from [The TVDB](https://thetvdb.com/auth/register)
-
-<tip>
-    If you want to use your own MetadataRelay, you can set the <code>tmdb_relay_url</code> and/or <code>tvdb_relay_url</code> to your own relay service.
-</tip>
-
-## Example Configuration
-
-Here's a complete example of the metadata section in your `config.toml`:
-
-```toml
-[metadata]
-    # TMDB configuration
-    [metadata.tmdb]
-    tmdb_relay_url = "https://metadata-relay.dorninger.co/tmdb"
-
-    # TVDB configuration  
-    [metadata.tvdb]
-    tvdb_relay_url = "https://metadata-relay.dorninger.co/tvdb"
-```
-
-<note>
-    In most cases, you can simply use the default values and don't need to specify these settings in your config file at all.
-</note>

Writerside/topics/notes.topic

@@ -1,19 +0,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE topic SYSTEM "https://resources.jetbrains.com/writerside/1.0/html-entities.dtd">
-<topic id="notes"
-       is-library="true" title="notes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-       xsi:noNamespaceSchemaLocation="https://resources.jetbrains.com/writerside/1.0/topic.v2.xsd">
-    <snippet id="list-format">
-        Lists have to be formatted like this: <code>["item1", "item2", "item3"]</code>. Note the double quotes.
-    </snippet>
-    <snippet id="auth-admin-emails">
-        <tip>
-            <p>When setting up MediaManager for the first time, you should add your email to <code>admin_emails</code>
-                in the <code>[auth]</code> config
-                section, MediaManager will then use this email instead of the default admin email. Your account will automatically be
-                created as an admin account, allowing you to manage other
-                users, media and
-                settings.</p>
-        </tip>
-    </snippet>
-</topic>

Writerside/topics/qBittorrent-Category.md

@@ -1,12 +0,0 @@
-# qBittorrent Category
-
-qBittorrent supports saving Torrents to subdirectories based on the category of the Torrent.
-The default category name that MediaManager uses is `MediaManager`.
-
-With the variable `torrents.qbittorrent.category_name` you can change the category name that MediaManager uses when
-adding Torrents to qBittorrent.
-
-With the variable `torrents.qbittorrent.category_save_path` you can change the path where the Torrents are saved to. By
-default, no subdirectory is used. Note that qBittorrent saves torrents to this path, so it must be a
-valid path that qBittorrent can write to. Example value: `/data/torrents/MediaManager`. Note that for MediaManager to be
-able to successfully import torrents, you must add the subdirectory to the `misc.torrent_directory` variable.

Writerside/topics/troubleshooting.md

@@ -1,46 +0,0 @@
-# Troubleshooting
-
-<tip>
-    Always check the container and browser logs for more specific error messages
-</tip>
-
-## Authentication Issues
-
-<procedure title="I can't log in with OAuth/OIDC?" id="procedure-i-cannot-log-in-with-oauth">
-    <step>Verify your OAuth provider's configuration. <a href="authentication-setup.md" anchor="openid-connect-settings-auth-openid-connect">See the OAuth documentation</a></step>
-    <step>Check if the callback URI you set in your OIDC providers settings is correct. <a href="authentication-setup.md" anchor="redirect-uri">See the callback URI documentation</a> </step>
-    <step>Check the frontend url in your config file. It should match the URL you use to access MediaManager.</step>
-</procedure>
-
-<procedure title="I cannot log in?" id="procedure-i-cannot-log-in">
-   <step>Make sure you are logging in, not signing up.</step>
-   <step>Try logging in with the following credentials: 
-        <list>
-          <li>Email: admin@mediamanager.local or admin@example.com</li>
-          <li>Password: admin</li>
-        </list>
-   </step>
-</procedure>
-
-## Hard linking Issues
-
-- Make sure you are using only one volumes for TV, Movies and Downloads.
-  <a href="https://raw.githubusercontent.com/maxdorninger/MediaManager/refs/heads/master/docker-compose.yaml"> See the configuration in the example <code>docker-compose.yaml</code> file.</a>
-
-The reason is that hard linking only works within the same filesystem. If your downloads are on a different volume than
-your media library, hard linking will not work.
-
-## Torrent Search Issues
-
-<procedure title="I get no search results for torrents?" id="procedure-i-get-no-search-results">
-    <step>Try switching to the advanced tab when searching for torrents.</step>
-    <step><a href="Indexer-Settings.md">If you use "slow" indexers, try increasing the timeout threshold.</a></step>
-    <step>If you still don't get any search results, check the logs, they will provide more information on what is going wrong.</step>
-</procedure>
-
-## Import and download Issues
-
-- If you configured a category with a special save path,
-  <a href="qBittorrent-Category.md">carefully read this page about MM with qBittorrent save paths.</a>
-
-<note>If it still doesn't work, <a href="https://github.com/maxdorninger/MediaManager/issues">please open an Issue.</a> It is possible that a bug is causing the issue.</note>

Writerside/v.list

@@ -1,5 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE vars SYSTEM "https://resources.jetbrains.com/writerside/1.0/vars.dtd">
-<vars>
-    <var name="product" value="Writerside"/>
-</vars>

Writerside/writerside.cfg

@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE ihp SYSTEM "https://resources.jetbrains.com/writerside/1.0/ihp.dtd">
-
-<ihp version="2.0">
-    <topics dir="topics" web-path="topics"/>
-    <images dir="images" web-path="MediaManager"/>
-    <instance src="mm.tree"/>
-    <instance src="Writerside_libraries.tree"/>
-</ihp>

alembic/env.py

@@ -1,13 +1,16 @@
 import sys
 
-sys.path = ["", ".."] + sys.path[1:]
+sys.path = ["", "..", *sys.path[1:]]
 
 
 from logging.config import fileConfig  # noqa: E402
 
+from sqlalchemy import (  # noqa: E402
+    engine_from_config,
+    pool,
+)
+
 from alembic import context  # noqa: E402
-from sqlalchemy import engine_from_config  # noqa: E402
-from sqlalchemy import pool  # noqa: E402
 
 # this is the Alembic Config object, which provides
 # access to the values within the .ini file in use.
@@ -23,34 +26,40 @@ if config.config_file_name is not None:
 # from myapp import mymodel
 # target_metadata = mymodel.Base.metadata
 
-from media_manager.auth.db import User, OAuthAccount  # noqa: E402
+from media_manager.auth.db import OAuthAccount, User  # noqa: E402
+from media_manager.config import MediaManagerConfig  # noqa: E402
+from media_manager.database import Base  # noqa: E402
 from media_manager.indexer.models import IndexerQueryResult  # noqa: E402
-from media_manager.torrent.models import Torrent  # noqa: E402
-from media_manager.tv.models import Show, Season, Episode, SeasonFile, SeasonRequest  # noqa: E402
 from media_manager.movies.models import Movie, MovieFile, MovieRequest  # noqa: E402
 from media_manager.notification.models import Notification  # noqa: E402
-from media_manager.database import Base  # noqa: E402
-from media_manager.config import MediaManagerConfig  # noqa: E402
+from media_manager.torrent.models import Torrent  # noqa: E402
+from media_manager.tv.models import (  # noqa: E402
+    Episode,
+    Season,
+    SeasonFile,
+    SeasonRequest,
+    Show,
+)
 
 target_metadata = Base.metadata
 
 # this is to keep pycharm from complaining about/optimizing unused imports
 # noinspection PyStatementEffect
-(
-    User,
-    OAuthAccount,
-    IndexerQueryResult,
-    Torrent,
-    Show,
-    Season,
-    Episode,
-    SeasonFile,
-    SeasonRequest,
-    Movie,
-    MovieFile,
-    MovieRequest,
-    Notification,
-)
+__all__ = [
+    "Episode",
+    "IndexerQueryResult",
+    "Movie",
+    "MovieFile",
+    "MovieRequest",
+    "Notification",
+    "OAuthAccount",
+    "Season",
+    "SeasonFile",
+    "SeasonRequest",
+    "Show",
+    "Torrent",
+    "User",
+]
 
 
 # other values from the config, defined by the needs of env.py,
@@ -60,19 +69,7 @@ target_metadata = Base.metadata
 
 
 db_config = MediaManagerConfig().database
-db_url = (
-    "postgresql+psycopg"
-    + "://"
-    + db_config.user
-    + ":"
-    + db_config.password
-    + "@"
-    + db_config.host
-    + ":"
-    + str(db_config.port)
-    + "/"
-    + db_config.dbname
-)
+db_url = f"postgresql+psycopg://{db_config.user}:{db_config.password}@{db_config.host}:{db_config.port}/{db_config.dbname}"
 
 config.set_main_option("sqlalchemy.url", db_url)
 
@@ -109,7 +106,13 @@ def run_migrations_online() -> None:
 
     """
 
-    def include_object(object, name, type_, reflected, compare_to):
+    def include_object(
+        _object: object | None,
+        name: str | None,
+        type_: str | None,
+        _reflected: bool | None,
+        _compare_to: object | None,
+    ) -> bool:
         if type_ == "table" and name == "apscheduler_jobs":
             return False
         return True

alembic/versions/16e78af9e5bf_add_original_language_columns_to_show_.py

@@ -8,9 +8,9 @@ Create Date: 2025-12-13 18:47:02.146038
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "16e78af9e5bf"

alembic/versions/1801d9f5a275_add_library_field_to_movie_and_show_.py

@@ -8,9 +8,9 @@ Create Date: 2025-07-16 01:09:44.045395
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "1801d9f5a275"

alembic/versions/1f340754640a_add_continuous_download_column_to_show_.py

@@ -8,9 +8,9 @@ Create Date: 2025-06-22 13:46:01.973406
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "1f340754640a"

alembic/versions/21a19f0675f9_increase_access_token_length.py

@@ -8,9 +8,9 @@ Create Date: 2025-07-06 10:49:08.814496
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "21a19f0675f9"

alembic/versions/2c61f662ca9e_add_imdb_id_fields.py

@@ -8,9 +8,9 @@ Create Date: 2025-12-23 19:42:09.593945
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "2c61f662ca9e"

alembic/versions/333866afcd2c_add_usenet_columns.py

@@ -8,9 +8,10 @@ Create Date: 2025-07-09 20:55:42.338629
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
+
 # revision identifiers, used by Alembic.
 revision: str = "333866afcd2c"
 down_revision: Union[str, None] = "aa4689f80796"

alembic/versions/5299dfed220b_add_score_field_to_indexerqueryresult_.py

@@ -8,9 +8,9 @@ Create Date: 2025-07-16 23:24:37.931188
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "5299dfed220b"

alembic/versions/7508237d5bc2_add_ended_column_to_show_table.py

@@ -8,9 +8,9 @@ Create Date: 2025-06-10 21:25:27.871064
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "7508237d5bc2"

alembic/versions/93fb07842385_initial_migration.py

@@ -8,10 +8,11 @@ Create Date: 2025-05-27 21:36:18.532068
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 from sqlalchemy.dialects import postgresql
 
+from alembic import op
+
 # revision identifiers, used by Alembic.
 revision: str = "93fb07842385"
 down_revision: Union[str, None] = None

alembic/versions/aa4689f80796_increase_refresh_token_length.py

@@ -8,9 +8,9 @@ Create Date: 2025-07-06 10:54:19.714809
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "aa4689f80796"

alembic/versions/eb0bd3cc1852_add_indexer_column_to_indexerqueryresult.py

@@ -8,9 +8,9 @@ Create Date: 2025-10-28 21:39:24.480466
 
 from typing import Sequence, Union
 
-from alembic import op
 import sqlalchemy as sa
 
+from alembic import op
 
 # revision identifiers, used by Alembic.
 revision: str = "eb0bd3cc1852"

config.dev.toml

@@ -1,6 +1,6 @@
 # MediaManager Dev Configuration File
 # This file contains all available configuration options for MediaManager
-# Documentation: https://maxdorninger.github.io/MediaManager/introduction.html
+# Documentation: https://maxdorninger.github.io/MediaManager/
 #
 # This is an example configuration file that gets copied to your config folder
 # on first boot. You should modify the values below to match your setup.

config.example.toml

@@ -1,6 +1,6 @@
 # MediaManager Example Configuration File
 # This file contains all available configuration options for MediaManager
-# Documentation: https://maxdorninger.github.io/MediaManager/introduction.html
+# Documentation: https://maxdorninger.github.io/MediaManager/
 #
 # This is an example configuration file that gets copied to your config folder
 # on first boot. You should modify the values below to match your setup.

docker-compose.dev.yaml

@@ -56,6 +56,15 @@ services:
       - ./web:/app
     depends_on:
       - mediamanager
+  docs:
+    image: squidfunk/mkdocs-material:9
+    container_name: mediamanager-docs
+    volumes:
+      - .:/docs
+    ports:
+      - "9000:9000"
+    command: serve -w /docs -a 0.0.0.0:9000
+
 
 # ----------------------------
 # Additional services can be uncommented and configured as needed
@@ -130,17 +139,17 @@ services:
 #    ports:
 #      - 8081:8080
 #    restart: unless-stopped
-#  jackett:
-#    image: lscr.io/linuxserver/jackett:latest
-#    container_name: jackett
-#    environment:
-#      - PUID=1000
-#      - PGID=1000
-#      - TZ=Etc/UTC
-#      - AUTO_UPDATE=true
-#    volumes:
-#      - ./res/jackett/data:/config
-#      - ./res/jackett/torrents:/downloads
-#    ports:
-#      - 9117:9117
-#    restart: unless-stopped
+  jackett:
+    image: lscr.io/linuxserver/jackett:latest
+    container_name: jackett
+    environment:
+      - PUID=1000
+      - PGID=1000
+      - TZ=Etc/UTC
+      - AUTO_UPDATE=true
+    volumes:
+      - ./res/jackett/data:/config
+      - ./res/jackett/torrents:/downloads
+    ports:
+      - 9117:9117
+    restart: unless-stopped

docker-compose.yaml

@@ -1,7 +1,7 @@
 services:
   mediamanager:
     container_name: mediamanager_server
-    image: ghcr.io/maxdorninger/mediamanager/mediamanager:latest
+    image: quay.io/maxdorninger/mediamanager:latest
     ports:
       - "8000:8000"
     environment:

docs/advanced-features/custom-port.md

@@ -0,0 +1,4 @@
+# Custom port
+
+* `PORT`\
+  Port that MediaManager listens on. Default is `8000`. This only works if you are using the Docker image. Configured as environment variable.

docs/advanced-features/disable-startup-ascii-art.md

@@ -0,0 +1,4 @@
+# Disable Startup Ascii Art
+
+* `MEDIAMANAGER_NO_STARTUP_ART`: Set this environment variable (to any value) \
+  to disable the colorized startup splash screen. Unset to reenable.

docs/advanced-features/follow-symlinks-in-frontend-files.md

@@ -0,0 +1,12 @@
+# Follow symlinks in frontend files
+
+MediaManager can be configured to follow symlinks when serving frontend files. This is useful if you have a setup where your frontend files are stored in a different location, and you want to symlink them into the MediaManager frontend directory.
+
+
+
+* `FRONTEND_FOLLOW_SYMLINKS`\
+  Set this environment variable to `true` to follow symlinks when serving frontend files. Default is `false`.
+
+```bash title=".env"
+FRONTEND_FOLLOW_SYMLINKS=true
+```

docs/advanced-features/metadata-provider-configuration.md

@@ -0,0 +1,65 @@
+# Metadata Provider Configuration
+
+## Metadata Provider Configuration
+
+Metadata provider settings are configured in the `[metadata]` section of your `config.toml` file. These settings control how MediaManager retrieves information about movies and TV shows.
+
+### TMDB Settings (`[metadata.tmdb]`)
+
+TMDB (The Movie Database) is the primary metadata provider for MediaManager. It provides detailed information about movies and TV shows.
+
+!!! info
+    Other software like Jellyfin use TMDB as well, so there won't be any metadata discrepancies.
+
+* `tmdb_relay_url`\
+  URL of the TMDB relay (MetadataRelay). Default is `https://metadata-relay.dorninger.co/tmdb`. Example: `https://your-own-relay.example.com/tmdb`.
+* `primary_languages`\
+  If the original language of a show/movie is in this list, metadata is fetched in that language. Otherwise, `default_language` is used. Default is `[]`. Example: `["no", "de", "es"]`. Format: ISO 639-1 (2 letters). Full list: https://en.wikipedia.org/wiki/List\_of\_ISO\_639\_language\_codes
+* `default_language`\
+  TMDB language parameter used when searching and adding. Default is `en`. Format: ISO 639-1 (2 letters).
+
+!!! warning
+    `default_language` sets the TMDB `language` parameter when searching and adding TV shows and movies. If TMDB does not find a matching translation, metadata in the original language will be fetched with no option for a fallback language. It is therefore highly advised to only use "broad" languages. For most use cases, the default setting is safest.
+
+### TVDB Settings (`[metadata.tvdb]`)
+
+!!! warning
+    The TVDB might provide false metadata and doesn't support some features of MediaManager like showing overviews. Therefore, TMDB is the preferred metadata provider.
+
+* `tvdb_relay_url`\
+  URL of the TVDB relay (MetadataRelay). Default is `https://metadata-relay.dorninger.co/tvdb`. Example: `https://your-own-relay.example.com/tvdb`.
+
+### MetadataRelay
+
+!!! info
+    To use MediaManager you don't need to set up your own MetadataRelay, as the default relay hosted by the developer should be sufficient for most purposes.
+
+The MetadataRelay is a service that provides metadata for MediaManager. It acts as a proxy for TMDB and TVDB, allowing you to use your own API keys if needed, but the default relay means you don't need to create accounts for API keys yourself.
+
+You might want to use your own relay if you want to avoid rate limits, protect your privacy, or for other reasons. If you know Sonarr's Skyhook, this is similar to that.
+
+#### Where to get API keys
+
+* Get a TMDB API key from [The Movie Database](https://www.themoviedb.org/settings/api)
+* Get a TVDB API key from [The TVDB](https://thetvdb.com/auth/register)
+
+!!! info
+    If you want to use your own MetadataRelay, you can set the `tmdb_relay_url` and/or `tvdb_relay_url` to your own relay service.
+
+### Example Configuration
+
+Here's a complete example of the metadata section in your `config.toml`:
+
+```toml title="config.toml"
+[metadata]
+    # TMDB configuration
+    [metadata.tmdb]
+    tmdb_relay_url = "https://metadata-relay.dorninger.co/tmdb"
+
+    # TVDB configuration
+    [metadata.tvdb]
+    tvdb_relay_url = "https://metadata-relay.dorninger.co/tvdb"
+```
+
+!!! info
+    In most cases, you can simply use the default values and don't need to specify these settings in your config file at all.

docs/advanced-features/qbittorrent-category.md

@@ -0,0 +1,16 @@
+# qBittorrent Category
+
+qBittorrent supports saving Torrents to subdirectories based on the category of the Torrent. The default category name that MediaManager uses is `MediaManager`.
+
+Use the following variables to customize behavior:
+
+* `torrents.qbittorrent.category_name`\
+  Category name MediaManager uses when adding torrents to qBittorrent. Default is `MediaManager`.
+* `torrents.qbittorrent.category_save_path`\
+  Save path for the category in qBittorrent. By default, no subdirectory is used. Example: `/data/torrents/MediaManager`.
+
+!!! info
+    qBittorrent saves torrents to the path specified by `torrents.qbittorrent.category_save_path`, so it must be a valid path that qBittorrent can write to.
+
+!!! warning
+    For MediaManager to successfully import torrents, you must add the subdirectory to the `misc.torrent_directory` variable.

docs/advanced-features/url-prefix.md

@@ -6,7 +6,7 @@ In order to run it on a prefixed path, like `maxdorninger.github.io/media`, the
 
 In short, clone the repository, then run:
 
-```
+```none title="Build Docker image"
 docker build \
   --build-arg BASE_PATH=/media \
   --build-arg VERSION=my-custom-version \
@@ -16,7 +16,10 @@ docker build \
 
 You also need to set the `BASE_PATH` environment variable at runtime in `docker-compose.yaml`:
 
-```yaml
+* `BASE_PATH`\
+  Base path prefix MediaManager is served under. Example: `/media`. This must match the `BASE_PATH` build arg.
+
+```yaml title="docker-compose.yaml (excerpt)"
 services:
   mediamanager:
     image: MediaManager:my-custom-version
@@ -27,8 +30,7 @@ services:
       ...
 ```
 
-<note>
-    Make sure to include the base path in the frontend_url field in the config file. For more information see the page on <a href="configuration-backend.md"><code>frontend_url</code></a>.
-</note>
+!!! info
+    Make sure to include the base path in the `frontend_url` field in the config file. See [Backend](../configuration/backend.md).
 
 Finally, ensure that whatever reverse proxy you're using leaves the incoming path unchanged; that is, you should not strip the `/media` from `/media/web/`.

docs/api-reference.md

@@ -0,0 +1,7 @@
+# API Reference
+
+!!! info
+    Media Manager's backend is built with FastAPI, which automatically generates interactive API documentation.
+
+* Swagger UI (typically available at `http://localhost:8000/docs`)
+* ReDoc (typically available at `http://localhost:8000/redoc`)

docs/configuration/README.md

@@ -0,0 +1,69 @@
+# Configuration
+
+MediaManager uses a TOML configuration file (`config.toml`) for all backend settings. This centralized configuration approach makes it easier to manage, backup, and share your MediaManager setup.
+
+Frontend settings are configured through environment variables in your `docker-compose.yaml` file.
+
+## Configuration File Location
+
+!!! warning
+    Note that MediaManager may need to be restarted for changes in the config file to take effect.
+
+Your `config.toml` file should be in the directory that's mounted to `/app/config/config.toml` inside the container:
+
+```yaml
+volumes:
+  - ./config:/app/config
+```
+
+You can change the configuration directory with the following environment variable:
+
+* `CONFIG_DIR`\
+  Directory that contains `config.toml`. Default is `/app/config`. Example: `/etc/mediamanager/`.
+
+## Configuration Sections
+
+The configuration is organized into the following sections:
+
+* `[misc]` - General settings
+* `[database]` - Database settings
+* `[auth]` - Authentication settings
+* `[notifications]` - Notification settings (Email, Gotify, Ntfy, Pushover)
+* `[torrents]` - Download client settings (qBittorrent, Transmission, SABnzbd)
+* `[indexers]` - Indexer settings (Prowlarr and Jackett )
+* `[metadata]` - TMDB and TVDB settings
+
+## Configuring Secrets
+
+For sensitive information like API keys, passwords, and secrets, you should use environment variables. You can actually set every configuration value through environment variables. For example, to set the `token_secret` value for authentication, with a .toml file you would use:
+
+```toml
+[auth]
+token_secret = "your_super_secret_key_here"
+```
+
+But you can also set it through an environment variable:
+
+```none
+MEDIAMANAGER_AUTH__TOKEN_SECRET = "your_super_secret_key_here"
+```
+
+or another example with the OIDC client secret:
+
+```toml
+[auth]
+...
+[auth.openid_connect]
+client_secret = "your_client_secret_from_provider"
+```
+
+env variable:
+
+```none
+MEDIAMANAGER_AUTH__OPENID_CONNECT__CLIENT_SECRET = "your_client_secret_from_provider"
+```
+
+So for every config "level", you basically have to take the name of the value and prepend it with the section names in uppercase with 2 underscores as delimiters and `MEDIAMANAGER_` as the prefix.
+
+!!! warning
+    Note that not every env variable starts with `MEDIAMANAGER_`; this prefix only applies to env variables which replace/overwrite values in the config file. Variables like the `CONFIG_DIR` env variable must not be prefixed.

docs/configuration/authentication.md

@@ -0,0 +1,81 @@
+---
+description: >-
+  MediaManager supports multiple authentication methods. Email/password
+  authentication is the default, but you can also enable OpenID Connect (OAuth
+  2.0) for integration with external identity providers
+---
+
+# Authentication
+
+All authentication settings are configured in the `[auth]` section of your `config.toml` file.
+
+## General Authentication Settings (`[auth]`)
+
+* `token_secret`\
+  Strong secret key for signing JWTs (create with `openssl rand -hex 32`). This is required.
+* `session_lifetime`\
+  Lifetime of user sessions in seconds. Default is `86400` (1 day).
+* `admin_emails`\
+  A list of email addresses for administrator accounts. This is required.
+* `email_password_resets`\
+  Enables password resets via email. Default is `false`.
+
+!!! info
+    To use email password resets, you must also configure SMTP settings in the `[notifications.smtp_config]` section.
+
+!!! info
+    When setting up MediaManager for the first time, you should add your email to `admin_emails` in the `[auth]` config section. MediaManager will then use this email instead of the default admin email. Your account will automatically be created as an admin account, allowing you to manage other users, media and settings.
+
+## OpenID Connect Settings (`[auth.openid_connect]`)
+
+OpenID Connect allows you to integrate with external identity providers like Google, Microsoft Azure AD, Keycloak, or any other OIDC-compliant provider.
+
+* `enabled`\
+  Set to `true` to enable OpenID Connect authentication. Default is `false`.
+* `client_id`\
+  Client ID provided by your OpenID Connect provider.
+* `client_secret`\
+  Client secret provided by your OpenID Connect provider.
+* `configuration_endpoint`\
+  OpenID Connect configuration endpoint URL. Do not include a trailing slash. Usually ends with `/.well-known/openid-configuration`.
+* `name`\
+  Display name for the OpenID Connect provider shown on the login page.
+
+### Configuration for your OpenID Connect Provider
+
+#### Redirect URI
+
+The OpenID server will likely require a redirect URI. This URL will usually look something like this:
+
+```none
+{MEDIAMANAGER_URL}/api/v1/auth/oauth/callback
+```
+
+!!! warning
+    It is very important that you set the correct callback URI, otherwise it won't work!
+
+#### Authentik Example
+
+Here is an example configuration for the OpenID Connect provider for Authentik.
+
+![authentik-redirect-url-example](<../assets/assets/authentik redirect url example.png>)
+
+## Example Configuration
+
+Here's a complete example of the authentication section in your `config.toml`:
+
+```toml title="config.toml"
+[auth]
+token_secret = "a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v2w3x4y5z6"
+session_lifetime = 604800  # 1 week
+admin_emails = ["admin@example.com", "manager@example.com"]
+email_password_resets = true
+
+[auth.openid_connect]
+enabled = true
+client_id = "mediamanager-client"
+client_secret = "your-secret-key-here"
+configuration_endpoint = "https://auth.example.com/.well-known/openid-configuration"
+name = "Authentik"
+```
+

docs/configuration/backend.md

@@ -0,0 +1,42 @@
+---
+description: >-
+  These settings configure the core backend application through the config.toml
+  file. All backend configuration is now centralized in this TOML file instead
+  of environment variables.
+---
+
+# Backend
+
+## General Settings (`[misc]`)
+
+*   `frontend_url`\
+    The URL the frontend will be accessed from. This is required. Do not include a trailing slash. Default is `http://localhost:8000`.
+
+    Example: if you are accessing MediaManager at `http://example.com/media`, set this to `http://example.com/media`.
+
+    If you are accessing MediaManager at the root of a domain, e.g. `https://mediamanager.example.com`, set this to `https://mediamanager.example.com`.
+
+    `frontend_url` does not affect where the server binds. It also does not configure a base path prefix. For prefixes, see [URL Prefix](../advanced-features/url-prefix.md).
+* `cors_urls`\
+  A list of origins you are going to access the API from. Do not include trailing slashes.
+* `development`\
+  Set to `true` to enable development mode. Default is `false`.
+
+## Example Configuration
+
+Here's a complete example of the general settings section in your `config.toml`:
+
+```toml title="config.toml"
+[misc]
+
+# REQUIRED: Change this to match your actual frontend domain.
+frontend_url = "http://mediamanager.dev"
+
+cors_urls = ["http://localhost:8000"]
+
+# Optional: Development mode (set to true for debugging)
+development = false
+```
+
+!!! info
+    The `frontend_url` is the most important setting to configure correctly. Make sure it matches your actual deployment URLs.

docs/configuration/custom-libraries.md

@@ -4,22 +4,20 @@ MediaManager supports custom libraries, allowing you to add multiple folders for
 
 ## Configuration
 
-Custom libraries are configured in the `mis` section in the `config.toml` file. You can add as many libraries as you need.
+Custom libraries are configured in the `misc` section in the `config.toml` file. You can add as many libraries as you need.
 
-<note>
-
-You are not limited to `/data/tv` or `/data/movies`, you can choose the entire path freely!
-
-</note>
+!!! info
+    You are not limited to `/data/tv` or `/data/movies`, you can choose the entire path freely!
 
 ### Movie Libraries
 
-To add custom movie libraries, you need to add a `[[misc.movie_libraries]]` section for each library. Each library requires a `name` and a `path`.
+To add custom movie libraries, add a `[[misc.movie_libraries]]` section for each library. Each library requires a `name` and a `path`.
 
-Here is an example of how to configure two movie libraries:
+Example — configuring two movie libraries:
 
 ```toml
 [misc]
+
 # ... other misc settings
 
 [[misc.movie_libraries]]
@@ -35,12 +33,13 @@ In this example, MediaManager will scan both `/data/movies/action` and `/data/mo
 
 ### TV Show Libraries
 
-Similarly, to add custom TV show libraries, you need to add a `[[misc.tv_libraries]]` section for each library. Each library requires a `name` and a `path`.
+Similarly, to add custom TV show libraries, add a `[[misc.tv_libraries]]` section for each library. Each library requires a `name` and a `path`.
 
-Here is an example of how to configure two TV show libraries:
+Example — configuring two TV show libraries:
 
 ```toml
 [misc]
+
 # ... other misc settings
 
 [[misc.tv_libraries]]
@@ -50,5 +49,4 @@ path = "/data/tv/live-action"
 [[misc.tv_libraries]]
 name = "Animation"
 path = "/data/tv/animation"
-
 ```

docs/configuration/database.md

@@ -0,0 +1,32 @@
+# Database
+
+Database settings are configured in the `[database]` section of your `config.toml` file. MediaManager uses PostgreSQL as its database backend.
+
+## Database Settings (`[database]`)
+
+* `host`\
+  Hostname or IP of the PostgreSQL server. Default is `localhost`.
+* `port`\
+  Port number of the PostgreSQL server. Default is `5432`.
+* `user`\
+  Username for the PostgreSQL connection. Default is `MediaManager`.
+* `password`\
+  Password for the PostgreSQL user. Default is `MediaManager`.
+* `dbname`\
+  Name of the PostgreSQL database. Default is `MediaManager`.
+
+## Example Configuration
+
+Here's a complete example of the database section in your `config.toml`:
+
+```toml title="config.toml"
+[database]
+host = "db"
+port = 5432
+user = "MediaManager"
+password = "your_secure_password"
+dbname = "MediaManager"
+```
+
+!!! info
+    In docker-compose deployments the container name is simultaneously its hostname, so you can use "db" or "postgres" as host.

docs/configuration/download-clients.md

@@ -6,93 +6,59 @@ Download client settings are configured in the `[torrents]` section of your `con
 
 qBittorrent is a popular BitTorrent client that MediaManager can integrate with for downloading torrents.
 
-- `enabled`
-
-Set to `true` to enable qBittorrent integration. Default is `false`.
-
-- `host`
-
-Hostname or IP of the qBittorrent server. Include the protocol (http/https).
-
-- `port`
-
-Port of the qBittorrent Web UI/API. Default is `8080`.
-
-- `username`
-
-Username for qBittorrent Web UI authentication. Default is `admin`.
-
-- `password`
-
-Password for qBittorrent Web UI authentication. Default is `admin`.
+* `enabled`\
+  Set to `true` to enable qBittorrent integration. Default is `false`.
+* `host`\
+  Hostname or IP of the qBittorrent server. Include the protocol (http/https).
+* `port`\
+  Port of the qBittorrent Web UI/API. Default is `8080`.
+* `username`\
+  Username for qBittorrent Web UI authentication. Default is `admin`.
+* `password`\
+  Password for qBittorrent Web UI authentication. Default is `admin`.
 
 ## Transmission Settings (`[torrents.transmission]`)
 
-<note>
-
-The downloads path in Transmission and MediaManager __must__ be the same, i.e. the path `/data/torrents` must link to the same volume for both containers.
-
-</note>
+!!! info
+    The downloads path in Transmission and MediaManager must be the same, i.e. the path `/data/torrents` must link to the same volume for both containers.
 
 Transmission is a BitTorrent client that MediaManager can integrate with for downloading torrents.
 
-- `enabled`
-
-Set to `true` to enable Transmission integration. Default is `false`.
-
-- `username`
-
-Username for Transmission RPC authentication.
-
-- `password`
-
-Password for Transmission RPC authentication.
-
-- `https_enabled`
-
-Set to `true` if your Transmission RPC endpoint uses HTTPS. Default is `true`.
-
-- `host`
-
-Hostname or IP of the Transmission server (without protocol).
-
-- `port`
-
-Port of the Transmission RPC endpoint. Default is `9091`.
-
-- `path`
-
-RPC request path target. Usually `/transmission/rpc`.
+* `enabled`\
+  Set to `true` to enable Transmission integration. Default is `false`.
+* `username`\
+  Username for Transmission RPC authentication.
+* `password`\
+  Password for Transmission RPC authentication.
+* `https_enabled`\
+  Set to `true` if your Transmission RPC endpoint uses HTTPS. Default is `true`.
+* `host`\
+  Hostname or IP of the Transmission server (without protocol).
+* `port`\
+  Port of the Transmission RPC endpoint. Default is `9091`.
+* `path`\
+  RPC request path target. Usually `/transmission/rpc`.
 
 ## SABnzbd Settings (`[torrents.sabnzbd]`)
 
 SABnzbd is a Usenet newsreader that MediaManager can integrate with for downloading NZB files.
 
-- `enabled`
-
-Set to `true` to enable SABnzbd integration. Default is `false`.
-
-- `host`
-
-Hostname or IP of the SABnzbd server, it needs to include `http(s)://`.
-
-- `port`
-
-Port of the SABnzbd API. Default is `8080`.
-
-- `api_key`
-
-API key for SABnzbd. You can find this in SABnzbd's configuration under "General" → "API Key".
-
-- `base_path`
-
-API base path for SABnzbd. It usually ends with `/api`, the default is `/api`.
+* `enabled`\
+  Set to `true` to enable SABnzbd integration. Default is `false`.
+* `host`\
+  Hostname or IP of the SABnzbd server, it needs to include `http(s)://`.
+* `port`\
+  Port of the SABnzbd API. Default is `8080`.
+* `api_key`\
+  API key for SABnzbd. You can find this in SABnzbd's configuration under "General" → "API Key".
+* `base_path`\
+  API base path for SABnzbd. It usually ends with `/api`, the default is `/api`.
 
 ## Example Configuration
 
 Here's a complete example of the download clients section in your `config.toml`:
 
-```toml
+```toml title="config.toml"
 [torrents]
     # qBittorrent configuration
     [torrents.qbittorrent]
@@ -124,7 +90,7 @@ Here's a complete example of the download clients section in your `config.toml`:
 
 When using Docker Compose, make sure your download clients are accessible from the MediaManager backend:
 
-```yaml
+```yaml title="docker-compose.yml"
 services:
   # MediaManager backend
   backend:
@@ -152,10 +118,8 @@ services:
     # ... other configuration ...
 ```
 
-<note>
+!!! warning
     You should enable only one BitTorrent and only one Usenet Download Client at any time.
-</note>
 
-<tip>
+!!! info
     Make sure the download directories in your download clients are accessible to MediaManager for proper file management and organization.
-</tip>

docs/configuration/indexers.md

@@ -0,0 +1,67 @@
+# Indexers
+
+Indexer settings are configured in the `[indexers]` section of your `config.toml` file. MediaManager supports both Prowlarr and Jackett as indexer providers.
+
+## Prowlarr (`[indexers.prowlarr]`)
+
+* `enabled`\
+  Set to `true` to enable Prowlarr. Default is `false`.
+* `url`\
+  Base URL of your Prowlarr instance.
+* `api_key`\
+  API key for Prowlarr. You can find this in Prowlarr's settings under General.
+* `timeout_seconds`\
+  Timeout in seconds for requests to Prowlarr. Default is `60`.
+
+!!! warning
+    Symptoms of timeouts are typically no search results ("No torrents found!") in conjunction with logs showing read timeouts.
+
+<details>
+
+<summary>Example timeout log</summary>
+
+```none
+DEBUG - media_manager.indexer.utils -
+ follow_redirects_to_final_torrent_url():
+  An error occurred during the request for <some-url>:
+   HTTPConnectionPool(host='<some-host>', port=<some-port>):
+    Read timed out. (read timeout=10)
+```
+
+</details>
+
+***
+
+## Jackett (`[indexers.jackett]`)
+
+* `enabled`\
+  Set to `true` to enable Jackett. Default is `false`.
+* `url`\
+  Base URL of your Jackett instance.
+* `api_key`\
+  API key for Jackett. You can find this in Jackett's dashboard.
+* `indexers`\
+  List of indexer names to use with Jackett.
+* `timeout_seconds`\
+  Timeout in seconds for requests to Jackett. Refer to the Prowlarr section for details.
+
+***
+
+## Example Configuration
+
+```toml title="config.toml"
+[indexers]
+[indexers.prowlarr]
+enabled = true
+url = "http://prowlarr:9696"
+api_key = "your_prowlarr_api_key"
+timeout_seconds = 60
+
+[indexers.jackett]
+enabled = false
+url = "http://jackett:9117"
+api_key = "your_jackett_api_key"
+indexers = ["1337x", "rarbg"]
+timeout_seconds = 60
+```
+

docs/configuration/logging.md

@@ -0,0 +1,12 @@
+# Logging
+
+MediaManager automatically logs events and errors to help with troubleshooting and monitoring. These logs are emitted to the console (stdout) by default, and to a json-formatted log file.
+
+## Configuring Logging
+
+The following are configured as environment variables.
+
+* `LOG_FILE`\
+  Path to the JSON log file. Default is `/app/config/media_manager.log`. The directory must exist and be writable.
+* `MEDIAMANAGER_LOG_LEVEL`\
+  Logging level. Default is `INFO`. Supported values: `DEBUG`, `INFO`, `WARNING`, `ERROR`.

docs/configuration/notifications.md

@@ -1,88 +1,63 @@
 # Notifications
 
-These settings are configured in the `[notifications]` section of your `config.toml` file. 
+These settings are configured in the `[notifications]` section of your `config.toml` file.
 
-### SMTP Configuration (`[notifications.smtp_config]`)
+## SMTP Configuration (`[notifications.smtp_config]`)
 
 For sending emails, MediaManager uses the SMTP protocol. You can use any SMTP server, like Gmail or SMTP2GO.
 
-- `smtp_host`
+* `smtp_host`\
+  Hostname of the SMTP server.
+* `smtp_port`\
+  Port of the SMTP server.
+* `smtp_user`\
+  Username for the SMTP server.
+* `smtp_password`\
+  Password (or app password) for the SMTP server.
+* `from_email`\
+  From-address used when sending emails.
+* `use_tls`\
+  Set to `true` to use TLS for the SMTP connection. Default is `true`.
 
-Hostname of the SMTP server.
+## Email Notifications (`[notifications.email_notifications]`)
 
-- `smtp_port`
+Controls which emails receive notifications.
 
-Port of the SMTP server.
+* `enabled`\
+  Set to `true` to enable email notifications. Default is `false`.
+* `emails`\
+  List of email addresses to send notifications to.
 
-- `smtp_user`
+## Gotify Notifications (`[notifications.gotify]`)
 
-Username for the SMTP server.
+* `enabled`\
+  Set to `true` to enable Gotify notifications. Default is `false`.
+* `api_key`\
+  API key for Gotify.
+* `url`\
+  Base URL of your Gotify instance. Do not include a trailing slash.
 
-- `smtp_password`
+## Ntfy Notifications (`[notifications.ntfy]`)
 
-Password or app password for the SMTP server.
+* `enabled`\
+  Set to `true` to enable Ntfy notifications. Default is `false`.
+* `url`\
+  URL of your ntfy instance plus the topic.
 
-- `from_email`
+## Pushover Notifications (`[notifications.pushover]`)
 
-Email address from which emails will be sent.
-
-- `use_tls`
-
-Set to `true` to use TLS for the SMTP connection. Default is `true`.
-
-### Email Notifications (`[notifications.email_notifications]`)
-
-- `enabled`
-
-Set to `true` to enable email notifications. Default is `false`.
-
-- `emails`
-
-List of email addresses to send notifications to.
-
-### Gotify Notifications (`[notifications.gotify]`)
-
-- `enabled`
-
-Set to `true` to enable Gotify notifications. Default is `false`.
-
-- `api_key`
-
-API key for Gotify.
-
-- `url`
-
-Base URL of your Gotify instance. Note the lack of a trailing slash.
-
-### Ntfy Notifications (`[notifications.ntfy]`)
-
-- `enabled`
-
-Set to `true` to enable Ntfy notifications. Default is `false`.
-
-- `url`
-
-URL of your ntfy instance plus the topic.
-
-### Pushover Notifications (`[notifications.pushover]`)
-
-- `enabled`
-
-Set to `true` to enable Pushover notifications. Default is `false`.
-
-- `api_key`
-
-API key for Pushover.
-
-- `user`
-
-User key for Pushover.
+* `enabled`\
+  Set to `true` to enable Pushover notifications. Default is `false`.
+* `api_key`\
+  API key for Pushover.
+* `user`\
+  User key for Pushover.
 
 ## Example Configuration
 
 Here's a complete example of the notifications section in your `config.toml`:
 
-```toml
+```toml title="config.toml"
 [notifications]
     # SMTP settings for email notifications and password resets
     [notifications.smtp_config]
@@ -116,6 +91,6 @@ Here's a complete example of the notifications section in your `config.toml`:
     user = "your_pushover_user_key"
 ```
 
-<note>
+
+!!! info
     You can enable multiple notification methods simultaneously. For example, you could have both email and Gotify notifications enabled at the same time.
-</note>

docs/configuration/scoring-rulesets.md

@@ -0,0 +1,133 @@
+# Scoring Rulesets
+
+Scoring rulesets in MediaManager allow you to flexibly control which releases are preferred or avoided when searching for media. Each ruleset is a collection of scoring rules that can be assigned to one or more libraries. When MediaManager evaluates releases, it applies the relevant ruleset(s) to adjust the score of each result, influencing which releases are selected for download.
+
+## How Rulesets Work
+
+* Rulesets are defined in the configuration and contain a list of rule names and the libraries they apply to.
+* Scoring rules can target keywords in release titles or specific indexer flags.
+* When searching for a release, MediaManager checks which library the media belongs to and applies the corresponding ruleset.
+
+## Rules
+
+Rules define how MediaManager scores releases based on their titles or indexer flags. You can create rules that:
+
+* Prefer releases with specific codecs (e.g., H.265 over H.264).
+* Avoid releases with certain keywords (e.g., "CAM", "TS", "Nuked").
+* Reject releases that do not meet certain criteria (e.g., non-freeleech releases).
+* and more.
+
+!!! info
+    The keywords and flags are compared case-insensitively.
+
+### Title Rules
+
+Title rules allow you to adjust the score of a release based on the presence (or absence) of specific keywords in the release title. This is useful for preferring or avoiding certain encodings, sources, or other characteristics that are typically included in release names.
+
+Each title rule consists of:
+
+* `name`\
+  A unique identifier for the rule.
+* `keywords`\
+  List of keywords to search for in the release title.
+* `score_modifier`\
+  Amount to add or subtract from the score if a keyword matches.
+* `negate`\
+  If `true`, the rule applies when none of the keywords are present.
+
+Examples for Title Rules
+
+```toml title="config.toml"
+[[indexers.title_scoring_rules]]
+name = "prefer_h265"
+keywords = ["h265", "hevc", "x265"]
+score_modifier = 100
+negate = false
+
+[[indexers.title_scoring_rules]]
+name = "avoid_cam"
+keywords = ["cam", "ts"]
+score_modifier = -10000
+negate = false
+```
+
+* The first rule increases the score for releases containing "h265", "hevc", or "x265".
+* The second rule heavily penalizes releases containing "cam" or "ts".
+
+If `negate` is set to `true`, the `score_modifier` is applied only if none of the keywords are found in the title.
+
+### Indexer Flag Rules
+
+Indexer flag rules adjust the score based on flags provided by the indexer (such as `freeleech`, `nuked`, etc). These flags are often used to indicate special properties or warnings about a release.
+
+Each indexer flag rule consists of:
+
+* `name`\
+  A unique identifier for the rule.
+* `flags`\
+  List of indexer flags to match.
+* `score_modifier`\
+  Amount to add or subtract from the score if a flag matches.
+* `negate`\
+  If `true`, the rule applies when none of the flags are present.
+
+Examples for Indexer Flag Rules
+
+```toml title="config.toml"
+[[indexers.indexer_flag_scoring_rules]]
+name = "reject_non_freeleech"
+flags = ["freeleech", "freeleech75"]
+score_modifier = -10000
+negate = true
+
+[[indexers.indexer_flag_scoring_rules]]
+name = "reject_nuked"
+flags = ["nuked"]
+score_modifier = -10000
+negate = false
+```
+
+* The first rule penalizes releases that do not have the "freeleech" or "freeleech75" flag.
+* The second rule penalizes releases that are marked as "nuked".
+
+If `negate` is set to `true`, the `score_modifier` is applied only if none of the flags are present on the release.
+
+## Example
+
+```toml title="config.toml"
+[[indexers.scoring_rule_sets]]
+name = "default"
+libraries = ["ALL_TV", "ALL_MOVIES"]
+rule_names = ["prefer_h265", "avoid_cam", "reject_nuked"]
+
+[[indexers.scoring_rule_sets]]
+name = "strict_quality"
+libraries = ["ALL_MOVIES"]
+rule_names = ["prefer_h265", "avoid_cam", "reject_non_freeleech"]
+```
+
+## Libraries
+
+The libraries that are mentioned in the preceding example are explained in greater detail in the [Library config section](custom-libraries.md).
+
+### Special Libraries
+
+You can use special library names in your rulesets:
+
+* `ALL_TV`: Applies the ruleset to all TV libraries.
+* `ALL_MOVIES`: Applies the ruleset to all movie libraries.
+* `Default`: Applies the ruleset to all media that is not part of a custom library.
+
+This allows you to set global rules for all TV or movie content, or provide fallback rules for uncategorized media.
+
+!!! info
+    You don't need to create lots of libraries with different directories, multiple libraries can share the same directory. You can set multiple (unlimited) libraries to the default directory `/data/movies` or `/data/tv` and use different rulesets with them.
+
+## Relation to Sonarr/Radarr Profiles
+
+MediaManager's scoring rules and rulesets system is an alternative to Sonarr's Quality, Custom, and Release Profiles. This system is designed to be more intuitive and flexible.
+
+* Quality Profiles: Use scoring rules to prefer or avoid certain codecs, resolutions, or other quality indicators.
+* Custom/Release Profiles: Use title or flag-based rules to match or exclude releases based on keywords or indexer flags.
+
+This approach provides a powerful and transparent way to fine-tune your automation.

docs/contributing-to-mediamanager/developer-guide.md

@@ -0,0 +1,449 @@
+---
+description: >-
+  This section is for those who want to contribute to Media Manager or
+  understand its internals.
+---
+
+# Developer Guide
+
+## Source Code directory structure
+
+* `media_manager/`: Backend FastAPI application
+* `web/`: Frontend SvelteKit application
+* `docs/`: Documentation (MkDocs)
+* `metadata_relay/`: Metadata relay service, also FastAPI
+
+## Special Dev Configuration
+
+### Environment Variables
+
+MediaManager uses various environment variables for configuration. In the Docker development setup (`docker-compose.dev.yaml`), most of these are automatically configured for you.
+
+#### Backend Variables
+
+* `BASE_PATH`\
+  Base path for the app (for subdirectory deployments).
+* `PUBLIC_VERSION`\
+  Version string displayed in `/api/v1/health`.
+* `FRONTEND_FILES_DIR`\
+  Directory for built frontend files (e.g. `/app/web/build` in Docker).
+* `MEDIAMANAGER_MISC__DEVELOPMENT`\
+  When set to `TRUE`, enables FastAPI hot-reloading in Docker.
+
+#### Frontend Variables
+
+* `PUBLIC_API_URL`\
+  API URL for backend communication (auto-configured via Vite proxy in Docker).
+* `PUBLIC_VERSION`\
+  Version string displayed in the frontend UI.
+* `BASE_PATH`\
+  Base path for frontend routing (matches backend `BASE_PATH`).
+
+#### Docker Development Variables
+
+* `DISABLE_FRONTEND_MOUNT`\
+  When `TRUE`, disables mounting built frontend files (allows separate frontend container).
+
+!!! info
+    This is automatically set in `docker-compose.dev.yaml` to enable the separate frontend development container
+
+#### Configuration Files
+
+* Backend: `res/config/config.toml` (created from `config.dev.toml`)
+* Frontend: `web/.env` (created from `.env.example`)
+
+## Contributing
+
+* Consider opening an issue to discuss changes before starting work
+
+## Setting up the Development Environment
+
+I use IntellijIdea with the Pycharm and Webstorm plugins to develop this, but this guide should also work with VSCode. Normally I'd recommend Intellij, but unfortunately only Intellij Ultimate has support for FastAPI and some other features.
+
+### Recommended VSCode Plugins
+
+* Python
+* Svelte for VSCode
+
+### Recommended Intellij/Pycharm Plugins
+
+* Python
+* Svelte
+* Pydantic
+* Ruff
+* VirtualKit
+
+### Recommended Development Workflow
+
+The recommended way to develop MediaManager is using the fully Dockerized setup with `docker-compose.dev.yaml`. This ensures you're working in the same environment as production and makes it easy for new contributors to get started without installing Python, Node.js, or other dependencies locally.
+
+The development environment includes:
+
+* Backend (FastAPI) with automatic hot-reloading for Python code changes
+* Frontend (SvelteKit/Vite) with Hot Module Replacement (HMR) for instant updates
+* Database (PostgreSQL) pre-configured and ready to use
+
+#### What supports hot reloading and what does not
+
+* Python code changes (.py files), Frontend code changes (.svelte, .ts, .css) and configuration changes (config.toml) reload automatically.
+* Changing the backend dependencies (pyproject.toml) requires rebuilding: `docker compose -f docker-compose.dev.yaml build mediamanager`
+* Changing the frontend dependencies (package.json) requires restarting the frontend container: `docker compose -f docker-compose.dev.yaml restart frontend`
+* Database migrations: Automatically run on backend container startup
+
+This approach eliminates the need for container restarts during normal development and provides the best developer experience with instant feedback for code changes.
+
+#### How the Frontend Connects to the Backend
+
+In the Docker development setup, the frontend and backend communicate through Vite's proxy configuration:
+
+* Frontend runs on: `http://localhost:5173` (exposed from Docker)
+* Backend runs on: `http://mediamanager:8000` (Docker internal network)
+* Vite proxy: Automatically forwards all `/api/*` requests from frontend to backend
+
+This means when your browser makes a request to `http://localhost:5173/api/v1/tv/shows`, Vite automatically proxies it to `http://mediamanager:8000/api/v1/tv/shows`. The `PUBLIC_API_URL` environment variable is set to use this proxy, so you don't need to configure anything manually.
+
+### Setting up the full development environment with Docker (Recommended)
+
+
+
+
+### Prepare config files
+
+Create config directory (only needed on first run) and copy example config files:
+
+```bash
+mkdir -p res/config # Only needed on first run
+cp config.dev.toml res/config/config.toml
+cp web/.env.example web/.env
+```
+
+
+
+### Start all services
+
+Recommended: Use make commands for easy development
+
+```bash
+# Recommended: Use make commands for easy development
+make up
+```
+
+Alternative: Use docker compose directly (if make is not available)
+
+```bash
+docker compose -f docker-compose.dev.yaml up
+```
+
+
+
+### Access the application
+
+* Frontend (with HMR): http://localhost:5173
+* Backend API: http://localhost:8000
+* Database: localhost:5432
+
+The default user email is `admin@example.com` and password is `admin`, these are printed out in the logs accessible with `make logs`.
+
+Now you can edit code and see changes instantly:
+
+* Edit Python files → Backend auto-reloads
+* Edit Svelte/TypeScript files → Frontend HMR updates in browser
+* Edit config.toml → Changes apply immediately
+
+
+!!! info
+    Run `make help` to see all available development commands including `make down`, `make logs`, `make app` (shell into backend), and more.
+
+## Setting up the backend development environment (Local)
+
+### Clone & prerequisites
+
+1. Clone the repository
+2. cd into repo root
+3. Install `uv`: https://docs.astral.sh/uv/getting-started/installation/
+4. Verify installation:
+
+```bash
+uv --version
+```
+
+### Install Python with uv
+
+```bash
+uv python install 3.13
+```
+
+### Create virtual environment
+
+```bash
+uv venv --python 3.13
+```
+
+### Install dependencies
+
+```bash
+uv sync
+```
+
+### Run database migrations
+
+```bash
+uv run alembic upgrade head
+```
+
+### Run the backend (development mode)
+
+```bash
+uv run fastapi run media_manager/main.py --reload --port 8000
+```
+
+### Formatting & linting
+
+* Format code:
+
+```bash
+ruff format .
+```
+
+* Lint code:
+
+```bash
+ruff check .
+```
+
+## Setting up the frontend development environment (Local, Optional)
+
+
+
+
+### Clone & change dir
+
+1. Clone the repository
+2. cd into repo root
+3. cd into `web` directory
+
+
+
+### Install Node.js (example using nvm-windows)
+
+I used nvm-windows:
+
+```powershell
+nvm install 24.1.0
+nvm use 24.1.0
+```
+
+If using PowerShell you may need:
+
+```powershell
+Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
+```
+
+
+
+### Create .env for frontend
+
+```bash
+cp .env.example .env
+```
+
+Update `PUBLIC_API_URL` if your backend is not at `http://localhost:8000`
+
+
+
+### Install dependencies and run dev server
+
+```bash
+npm install
+npm run dev
+```
+
+
+
+### Format & lint
+
+* Format:
+
+```bash
+npm run format
+```
+
+* Lint:
+
+```bash
+npm run lint
+```
+
+
+!!! info
+    If running frontend locally, make sure to add `http://localhost:5173` to the `cors_urls` in your backend config file.
+
+## Troubleshooting
+
+### Common Docker Development Issues
+
+<details>
+
+<summary>Port already in use errors</summary>
+
+* Check if ports 5173, 8000, or 5432 are already in use:
+  * macOS/Linux: `lsof -i :5173`
+  * Windows: `netstat -ano | findstr :5173`
+* Stop conflicting services or change ports in `docker-compose.dev.yaml`
+
+</details>
+
+<details>
+
+<summary>Container not showing code changes</summary>
+
+* Verify volume mounts are correct in `docker-compose.dev.yaml`
+* For backend: Ensure `./media_manager:/app/media_manager` is mounted
+* For frontend: Ensure `./web:/app` is mounted
+* On Windows: Check that file watching is enabled in Docker Desktop settings
+
+</details>
+
+<details>
+
+<summary>Frontend changes not updating</summary>
+
+* Check that the frontend container is running: `make ps` or `docker compose -f docker-compose.dev.yaml ps`
+* Verify Vite's file watching is working (should see HMR updates in browser console)
+* Try restarting the frontend container:
+
+```bash
+docker compose -f docker-compose.dev.yaml restart frontend
+```
+
+</details>
+
+<details>
+
+<summary>Backend changes not reloading</summary>
+
+* Verify `MEDIAMANAGER_MISC__DEVELOPMENT=TRUE` is set in `docker-compose.dev.yaml`
+* Check backend logs:
+
+```bash
+make logs ARGS="--follow mediamanager"
+# or
+docker compose -f docker-compose.dev.yaml logs -f mediamanager
+```
+
+* If dependencies changed, rebuild:
+
+```bash
+docker compose -f docker-compose.dev.yaml build mediamanager
+```
+
+</details>
+
+<details>
+
+<summary>Database migration issues</summary>
+
+* Migrations run automatically on container startup
+* To run manually:
+
+```bash
+make app
+uv run alembic upgrade head
+```
+
+* To create new migration:
+
+```bash
+make app
+uv run alembic revision --autogenerate -m "description"
+```
+
+</details>
+
+<details>
+
+<summary>Viewing logs</summary>
+
+* All services: `make logs`
+* Follow logs in real-time: `make logs ARGS="--follow"`
+* Specific service: `make logs ARGS="mediamanager --follow"`
+
+</details>
+
+<details>
+
+<summary>Interactive debugging (shell into containers)</summary>
+
+* Shell into backend:
+
+```bash
+make app
+# or
+docker compose -f docker-compose.dev.yaml exec -it mediamanager bash
+```
+
+* Shell into frontend:
+
+```bash
+make frontend
+# or
+docker compose -f docker-compose.dev.yaml exec -it frontend sh
+```
+
+* Once inside, you can run commands like `uv run alembic upgrade head`, `npm install`, etc.
+
+</details>
+
+<details>
+
+<summary>Volume permission issues (Linux)</summary>
+
+* Docker containers may create files as root, causing permission issues, which can make the login page fail to show up.
+
+Solution:
+
+```bash
+sudo chown -R $USER:$USER res/
+```
+
+* Alternatively: Run containers with your user ID or use Docker's `user:` directive (may fail in some setups).
+
+</details>
+
+<details>
+
+<summary>Complete reset</summary>
+
+If all else fails, you can completely reset your development environment:
+
+```bash
+make down
+docker compose -f docker-compose.dev.yaml down -v  # Remove volumes
+docker compose -f docker-compose.dev.yaml build --no-cache  # Rebuild without cache
+make up
+```
+
+</details>
+
+## Tech Stack
+
+### Backend
+
+* Python
+* FastAPI
+* SQLAlchemy
+* Pydantic and Pydantic-Settings
+* Alembic
+
+### Frontend
+
+* TypeScript
+* SvelteKit
+* Tailwind CSS
+* shadcn-svelte
+* openapi-ts
+* openapi-fetch
+
+### CI/CD
+
+* GitHub Actions

docs/contributing-to-mediamanager/documentation.md

@@ -0,0 +1,14 @@
+# Documentation
+
+MediaManager uses [MkDocs](https://www.mkdocs.org/) with
+the [Material for MkDocs](https://squidfunk.github.io/mkdocs-material/) theme for documentation.
+
+The files for the documentation are in the `/docs` directory.
+
+To preview the documentation locally, you need to have mkdocs or Docker installed.
+
+## How to preview the documentation locally with docker
+
+1. Run the mkdocs container in `docker-compose.dev.yaml`
+
+2. Open `http://127.0.0.1:9000/` in your browser.

docs/importing-existing-media.md

@@ -0,0 +1,63 @@
+# Importing existing media
+
+In order for MediaManager to be able to import existing media (e.g. downloaded by Sonarr or Radarr) two conditions have to be met:
+
+* The folder's name must not start with a dot.
+* The media must be in the root tv/movie library.
+
+Here is an example, using these rules:
+
+```
+/
+└── data/
+    ├── tv/
+    │   ├── Rick and Morty                          # WILL be imported
+    │   ├── Stranger Things (2016) {tvdb_12345} [x265]  # WILL be imported
+    │   ├── Breaking Bad (2008) [tmdbid-1396]      # WILL be imported
+    │   ├── .The Office (2013)                     # WILL NOT
+    │   └── my-custom-library/
+    │       └── The Simpsons                       # WILL NOT be imported
+    └── movie/
+        └── Oppenheimer (2023)                    # WILL be imported
+```
+
+If your folder structure is in the correct format, you can start importing. To do this, log in as an administrator and go to the TV/movie dashboard.
+
+!!! info
+    After importing, MediaManager will automatically prefix the old root TV show/movie folders with a dot to mark them as "imported".
+
+So after importing, the directory would look like this (using the above directory structure):
+
+```
+/
+└── data/
+    ├── tv/
+    │   ├── .Rick and Morty                          # RENAMED
+    │   ├── Rick and Morty (2013) [tmdbid-60625]     # IMPORTED
+    │   ├── .Stranger Things (2016) {tvdb_12345}    # RENAMED
+    │   ├── Stranger Things (2016) [tmdbid-66732]    # IMPORTED
+    │   ├── .The Office (2013)                       # IGNORED
+    │   ├── .Breaking Bad (2008) [tmdbid-1396]       # RENAMED
+    │   ├── Breaking Bad (2008) [tmdbid-1396]        # IMPORTED
+    │   └── my-custom-library/
+    │       └── The Simpsons                         # IGNORED
+    └── movie/
+        ├── .Oppenheimer (2023)                      # RENAMED
+        └── Oppenheimer (2023) [tmdbid-872585]       # IMPORTED
+```
+
+## More criteria for importing
+
+These are the criteria specifically for the files themselves:
+
+* Movie folders (e.g. `Oppenheimer (2023)`) must contain exactly one video file (e.g. .mp4, .mkv).
+* The specific structure of season folders or episode folders or naming of them does not matter.
+* Episode files (video and subtitle files) must contain the season and episode number in their name, e.g. `S01E01.mp4` or `S03E07 Rick and Morty.mkv`.
+
+## Miscellaneous information
+
+* Make MediaManager ignore directories by prefixing them with a dot.
+* After importing, especially TV shows, manually check if all files are in the right place.
+* MediaManager outputs in the logs if an episode/movie could not be imported.
+
+Last updated: 20 December 2025