Migration

Migration from AniWorld Downloader

🌐 English · Deutsch

MediaForge was formerly called AniWorld Downloader / MRX-AniWorld-Downloader. If you used the old version, you don't have to do anything — your data is carried over automatically.

Automatic import on first start

The old version stored everything in ~/.aniworld. MediaForge uses ~/.mediaforge. The first time MediaForge starts, it checks for an old installation and, if the new directory has no database yet, copies your data over before the web interface comes up. That's why everything is already there the first time you open the UI.

What gets imported:

• the database (aniworld.db → mediaforge.db): settings, download history, queue, users, watchlist, favourites, library
• the .env file and secrets (.flask_secret, encrypted session data)
• the browser profile used for captcha solving
• image cache, keyword cache and push-notification data

The import is non-destructive — your old ~/.aniworld folder is never modified or deleted. If anything goes wrong you can always fall back to it.

A marker file ~/.mediaforge/.legacy_imported.json records what was copied and when.

Settings card

Under Settings → General you'll find a "Data from previous installation" card when an old install is detected. It lets you:

• Import remaining files — re-runs the copy for any files that are still missing. It never overwrites an existing database, so once the automatic import has run this usually reports "nothing left to import".
• Hide — dismisses the card for good (stored server-side, stays hidden after restarts and on other devices). Use this once you're done, or if you don't want to import at all.

Environment variables

All configuration variables were renamed from the ANIWORLD_ prefix to MEDIAFORGE_. Old ANIWORLD_ variables still work as a fallback, so existing .env files, shell exports and Docker setups keep running. An explicitly set MEDIAFORGE_ value always wins over the legacy one.

Docker

The container now runs as the mediaforge user and stores data in /home/mediaforge/.mediaforge. To bring your old data into a Docker install, mount the old volume so the app can find it on first start, e.g.:

# make the old data visible at ~/.aniworld inside the container → auto-import runs
-v aniworld-data:/home/mediaforge/.aniworld
# ...and the new persistent location
-v mediaforge-data:/home/mediaforge/.mediaforge

After the first start the data lives in mediaforge-data; you can drop the old mount afterwards.

Forcing a fresh import

The automatic import only runs when ~/.mediaforge/mediaforge.db does not exist yet. To import again from scratch, stop MediaForge, remove or rename ~/.mediaforge, and start again — the data will be copied fresh from ~/.aniworld.