Self-host Readeck with Levelrail
VerifiedSave the readable content of web pages you want to keep, free of ads and clutter.
- Memory256 MiB
- Archarm64
- Services1
How to self-host Readeck
-
Pull the images
One image is pulled on your server.
Show images
codeberg.org/readeck/readeck:0.23.4
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8000.
-
Fill in the secrets
You do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Readeck requirements
- Memory
- About 256 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 8000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Verified. Verified on arm64 with image tag 0.23.4. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 8000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Readeck. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Readeck docs page.
Deploy Readeck your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Readeck from the CLI
levelrail-cli templates deploy readeck --name my-readeck Deploy Readeck with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/readeck/deploy Readeck configuration
Readeck services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| readeck | codeberg.org/readeck/readeck:0.23.4 | 8000 | readeck_data -> /readeck |
Readeck environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8000
- Volumes
- 1 named mount: readeck_data -> /readeck
Readeck FAQ
How much memory does Readeck need?
The catalog lists about 256 MiB of memory for Readeck.
Does Readeck run on arm64?
For Readeck, arm64 is tested; amd64 is image published.
Does Readeck need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Readeck use?
Readeck listens on port 8000 inside the stack.
Where does Readeck keep its data?
In a named volume: readeck_data mounted at /readeck.
Can I deploy Readeck on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Readeck, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image codeberg.org/readeck/readeck:0.23.4 is what you deploy there.