ERDB generates poster/backdrop/logo/thumbnail images with dynamic ratings on-the-fly.
Click to view Self-Hosting Instructions (Docker / Local)
git clone https://github.com/realbestia1/erdb
cd erdb- Install dependencies:
sudo npm install - Build:
npm run build - Start the app:
npm run start - App available at
http://localhost:3000
By default, npm run start now launches the standalone server in multi-process mode and uses all available CPU cores on the machine. You can override it with ERDB_WORKERS=<n> npm run start, or force single-process mode with npm run start:single.
For high performance (on-the-fly image rendering), a server with a strong CPU and plenty of RAM is recommended.
Minimum recommended:
- CPU: 4 vCPU
- RAM: 4 GB
Basic start:
docker compose up -d --buildDocker now runs a single app container in multi-process mode. By default it uses ERDB_WORKERS=auto, so the container starts one worker per available CPU core. You can pin a fixed number with ERDB_WORKERS=4 docker compose up -d --build.
Run the published image directly:
docker pull ghcr.io/realbestia1/erdb:latest
docker run -d \
--name erdb \
-p 3000:3000 \
-v ./data:/app/data \
ghcr.io/realbestia1/erdb:latestUpdate the published image:
docker pull ghcr.io/realbestia1/erdb:latest
docker stop erdb
docker rm erdb
docker run -d \
--name erdb \
-p 3000:3000 \
-v ./data:/app/data \
ghcr.io/realbestia1/erdb:latestThe public port is ERDB_HTTP_PORT (default 3000) exposed directly by the app container. Set it in the .env file.
Data (SQLite database and image cache) is persisted in ./data.
Custom port:
ERDB_HTTP_PORT=4000 docker compose up -d --buildThe repository includes a GitHub Actions workflow at .github/workflows/docker-image.yml.
- On pull requests, it verifies that the Docker image builds successfully.
- On pushes to
main, it builds and publishes the image toghcr.io/<owner>/<repo>. - On tags like
v1.0.0, it also publishes a versioned image tag.
Click to view HuggingFace instructions (to avoid bans)
(to avoid bans on HuggingFace)
- Go to the ERDB GitHub repo: https://github.com/realbestia1/erdb
- Click the "Fork" button in the top-right corner
- Choose any name for the fork (do not use "erdb")
- Create a new Space
- Choose any name
- Select Docker
- Select Blank
- Set it as a Public space
- Click Create Space
Now click "Create the Dockerfile" (near the bottom of the page).
Copy and paste the content of Dockerfile.hf into the editor that opens,
replacing "realbestia1" with your GitHub username.
Line to change:
RUN git clone https://github.com/realbestia1/erdb.git .
After the edit, click "Commit new file to main".
To get your personal link:
- Click the three dots in the top-right corner
- Go to "Embed this Space"
- Copy the Direct URL
Done! Your ERDB is ready to use on HuggingFace.
Note: to update ERDB quickly, go to the Space settings and click "Factory Rebuild" only after syncing your fork on GitHub.
Full documentation, interactive API builder, and Addon generator are available on our official website:
Please configure your instance and obtain the erdbConfig payload directly from the website.
Our interactive configuration tool provides the easiest way to generate the required base64url configurations for Addon Developers.
ERDB can act as a proxy for any Stremio addon and always replace images (poster, background, logo, thumbnail) with the ones generated by ERDB.
Stremio does not use query params here. You must generate the link from the ERDB site using the "Addon Proxy" section:
https://YOUR_ERDB_HOST/proxy/{config}/manifest.json
{config} is created automatically by the site based on the inserted parameters.
- The proxy rewrites enabled
meta.poster,meta.background,meta.logo, andmeta.videos[].thumbnail(types can be toggled in the Addon Proxy UI). - The
urlfield must point to the original addon'smanifest.json. tmdbKeyandmdblistKeyare required.
for.supported.addons.mp4
for.unsupported.addons.mp4
© 2026 ERDB Project