Sources for the container images of Tangled Knot server, used to run knot.hackclub.community at an Azure VM (previously on Nest tilde server before going with Promox VM-based containers).

Usage#

On the repository creation page, select knot.hackclub.community as the Knot server. When cloning or adding/updating remote URLs, use the following SSH Git URLs below as documented:

# on its custom domain
git remote add origin ssh://git@knot.hackclub.community:33939/handle.host.tld/repo

# directly with our proxyparty server's hostname (since it's just a CNAME DNS record)
git remote add origin ssh://git@proxyparty.recaptime.dev:33939/handle.host.tld/repo

Infrastructure Operations#

Image CI builds happen via GitLab CI: https://gitlab.com/recaptime-dev/infra/knot-server-docker/pipelines
- View our GitLab CI config
- View tags on GitLab Container Registry
Run using built images after ssh recaptime-dev@hackclub.app: <docker|podman> compose up --no-build --force-recreate
Get build information: <docker|podman> compose exec knot knotserver-version

Requesting access#

You'll be asked for your AT Proto handle/DID PLC to provision access. Don't have one? You can sign up via Bluesky Social or in Tangled directly.

Hack Clubbers can request access for knot.hackclub.community by contacting Andrei Jiroh in the Slack, either via DMs or at the main #recaptime-dev Slack channel.

Docs#

License#

MIT

Configure Feed