Container Backend

Container Backend

Richmack Services is the backend for operations that should not live directly inside webpage JavaScript.

Image

ghcr.io/iamrichmack111/richmack-browser-services:v0.6.0

Pull

docker pull ghcr.io/iamrichmack111/richmack-browser-services:v0.6.0

Run

docker run -d \
  --name richmack-browser-services \
  -p 127.0.0.1:8765:8765 \
  -v "$HOME/Downloads/Richmack:/downloads" \
  ghcr.io/iamrichmack111/richmack-browser-services:v0.6.0

Why containerize the backend?

Advantages:

• dependency isolation
• repeatable distribution
• easier upgrades
• reduced host pollution
• clearer security boundary

Why not containerize Chromium?

Running the desktop browser itself inside Docker creates unnecessary problems around:

• graphics
• input
• file access
• desktop integration
• performance
• OS-native behavior

The browser stays native.