Self-host Isso with Levelrail
A lightweight self-hosted comment server for static sites with a small JavaScript embed. Comments live in a SQLite file on a volume.
- Authorisso-comments
- LicenceMIT
- Memory128 MiB
- Services1
How to self-host Isso
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/isso-comments/isso:0.14.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 8080.
-
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.
Isso requirements
- Memory
- About 128 MiB
- Architectures
- amd64 unknown, arm64 unknown
- Ports
- 8080
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Isso. 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 Isso docs page.
Deploy Isso your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Isso from the CLI
levelrail-cli templates deploy isso --name my-isso Deploy Isso with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/isso/deploy Isso configuration
Isso services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| isso | ghcr.io/isso-comments/isso:0.14.0 | 8080 | db -> /db |
Isso environment variables
The catalog lists no environment variables for this template.
Ports and volumes
- Ports
- 8080
- Volumes
- 1 named mount: db -> /db
Isso FAQ
How much memory does Isso need?
The catalog lists about 128 MiB of memory for Isso.
Does Isso run on arm64?
For Isso, arm64 support is not confirmed; amd64 is unknown.
What licence is Isso under?
Isso is licensed under MIT, which is permissive, with few conditions on reuse.
Does Isso need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Isso use?
Isso listens on port 8080 inside the stack.
Where does Isso keep its data?
In a named volume: db mounted at /db.
Can I deploy Isso 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 Isso, 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 ghcr.io/isso-comments/isso:0.14.0 is what you deploy there.