isso v0.1.0

Dev tools

Isso — a lightweight self-hosted commenting server (a Disqus alternative) you embed on your blog or static site: threaded comments, Markdown, moderation, no tracking. Deployed as a single host-networked Nomad service with SQLite and a seeded config.

nomad-pack run isso --registry nomploy

…or one line (add registry + run)

curl -fsSL https://packs.nomploy.com/install.sh | sh -s -- isso

Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.

Source ↗ Project ↗ ★ 5.3k ⚑ Report an issue

1 task http 8080 1 volume image ghcr.io/isso-comments/isso:latest tracks :latest image bumped today

Variables 9

values.hcl

Save as values.hcl, edit, then run:

nomad-pack run isso -f values.hcl --registry nomploy

# The name of the Nomad job.
job_name = "isso"

# The Nomad namespace to deploy into.
namespace = "default"

# The datacenters to deploy to.
datacenters = ["*"]

# The Isso container image. Pin a tag in production.
image = "ghcr.io/isso-comments/isso:latest"

# Host port for the Isso API.
port = 8080

# The website URL(s) where comments are embedded (comma-separated). Isso only accepts comments from these origins — set this to your blog's URL.
host = "http://localhost"

# Named volume for the SQLite comments database.
data_volume = "isso_data"

# Placement constraints. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []

# Resources for the Isso task.
resources = {
    cpu    = 200
    memory = 128
  }

Name	Type	Default	Description
job_name	string	"isso"	The name of the Nomad job.
namespace	string	"default"	The Nomad namespace to deploy into.
datacenters	list	["*"]	The datacenters to deploy to.
image	string	"ghcr.io/isso-comments/isso:latest"	The Isso container image. Pin a tag in production.
port	number	8080	Host port for the Isso API.
host	string	"http://localhost"	The website URL(s) where comments are embedded (comma-separated). Isso only accepts comments from these origins — set this to your blog's URL.
data_volume	string	"isso_data"	Named volume for the SQLite comments database.
constraints	list	[]	Placement constraints. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
resources	object	{ cpu = 200 memory = 128 }	Resources for the Isso task.

Back up this pack

This pack stores data in one Docker named volume: isso_data

restic

# Run on the node hosting this pack. Point restic at your repo first:
#   export RESTIC_REPOSITORY="s3:https://<account>.r2.cloudflarestorage.com/<bucket>"
#   export RESTIC_PASSWORD="<repo-password>"
#   export AWS_ACCESS_KEY_ID=<key>  AWS_SECRET_ACCESS_KEY=<secret>
restic backup \
  /var/lib/docker/volumes/isso_data/_data

rclone (sync to S3/R2)

rclone sync /var/lib/docker/volumes/isso_data/_data backup:<bucket>/isso_data

Paths assume the default Docker volume location (/var/lib/docker/volumes). Restore by stopping the job, restoring files into the same volume, and re-running the pack.

Readme

isso

Isso is a lightweight, self-hosted commenting server — a Disqus alternative you embed on your blog or static site. Threaded comments, Markdown, moderation and email notifications, with no tracking and no third parties.

This pack runs Isso as a single host-networked Nomad job with SQLite storage (in the isso_data volume) and a seeded config — no external database is required.

Quick start

nomad-pack run isso --registry=nomploy --var host=https://blog.example.com

Then embed it on your pages:

<script data-isso="http://<node-ip>:8080/"
        src="http://<node-ip>:8080/js/embed.min.js"></script>
<section id="isso-thread"></section>

Configuration

Variable	Default	Notes
`port`	`8080`	API host port
`host`	`http://localhost`	Set this to your site's URL — Isso only accepts comments from matching origins
`data_volume`	`isso_data`	SQLite comments database

Set host to the public URL of the site where comments are embedded; the default won't accept comments from a real site. For moderation, admin login and email notifications, extend the rendered config per the Isso docs.

Ideally serve Isso behind a reverse proxy on the same domain as your site.