Skip to content

Render

The repository has a Render Blueprint (deploy/render.yaml) that creates the collector as a Docker web service and a Render PostgreSQL 17 database, wires DATABASE_URL, and generates the session secret and settings key.

  1. Create the Blueprint

    In Render, choose New → Blueprint, connect your fork of Shardlens and set Blueprint path to deploy/render.yaml. Render shows the shardlens service and the shardlens-db database.

  2. Fill in the variables Render asks for

    Variable Value
    SHARDLENS_PUBLIC_URL Your service URL, for example https://shardlens.onrender.com
    SHARDLENS_APP_ID Your Discord application ID
    SHARDLENS_INGEST_KEY npx shardlens keys --scope ingest
    SHARDLENS_READ_KEY npx shardlens keys --scope read

    The service URL is https:// followed by the service name and .onrender.com, but Render adds a few characters when that name is taken. After the first deploy, compare it with the URL at the top of the service’s page and, if they differ, correct SHARDLENS_PUBLIC_URL under Environment: Discord sign-in and the links in alerts and reports use it.

    Leave DISCORD_CLIENT_ID, DISCORD_CLIENT_SECRET and DISCORD_PUBLIC_KEY empty unless you want Discord sign-in or webhook events. SHARDLENS_SESSION_SECRET and SHARDLENS_SETTINGS_KEY are generated for you; copy the settings key somewhere safe, because encrypted settings can’t be read without it.

  3. Apply. Render builds the image, the collector applies its migrations, and the health check on /readyz turns green.