Skip to content

Releases

v0.16.0

Choose a tag to compare

@github-actions github-actions released this 22 Nov 18:02
v0.16.0
570d452

Added

  • Static sites (ADR 0052): an app of
    kind static is an image with only its built files in /site (FROM scratch,
    COPY dist /site). Spotcraft serves them with its own server, Caddy from Spotcraft's image,
    with compression, clean URLs, immutable caching for hashed assets, and a fallback of 404
    (the site's 404.html) or spa (its index.html). It gets HTTPS, the headers, legal.json,
    analytics and the user pool like any app, and no env, schema or mail. The dashboard's Add
    app
    chooses App or Static site; the guide is docs/guides/static-sites.md. The agent gets
    SPOTCRAFT_SERVER_IMAGE from the server's Compose file, and moves static sites to a new
    Spotcraft version when it starts.
  • Redirects (ADR 0052): domains that
    send every request elsewhere with a 301, optionally keeping the path, with prefix rules first.
    An instance setting in Settings → Redirects, and GET, PUT and DELETE /redirects in
    the agent's API.

v0.15.0

Choose a tag to compare

@github-actions github-actions released this 22 Nov 16:19
v0.15.0
1f72a3c

Changed

  • Analytics through Spotless (ADR 0050): a new
    spotless service serves /_spotcraft/s.js and takes /_spotcraft/e on every app domain,
    then hands events to Umami. The tracker and the event format are Spotcraft's own now, written
    in the contract; Umami's tracker and collect endpoint are no longer reachable.
    Migration: nothing for pages that load s.js. For one release, config.json keeps
    websiteId, and the tracker honours umami.disabled and window.umami.track, so spotkit 0.3
    keeps working; move to spotkit 0.4. A client that posted Umami's payload to /e itself sends
    the new JSON instead.
  • The user pool contract (ADR 0049): the calls apps
    make are written out in our own terms; Spotpass is the reference implementation, and Better
    Auth's client keeps working with it.

Added

  • Check your instance: a guide to whoami, a small app
    that checks the database, migrations, mail, backups, the user pool, legal facts and analytics
    (ADR 0048).

Removed

  • Apps with their own database (ADR 0051):
    every app lives in its schema of the apps database. The agent's POST /apps/:name/move and
    GET /apps/:name/database, the dashboard's Own database form, and the CLI's own-database
    settings are gone. Backups and purges handle schemas only.
    Migration: before upgrading, move any app that still has its own database into its schema
    with 0.14 (the dashboard's Settings → Own database); then upgrade.
  • @spotcraft/kit (ADR 0051): the
    package, its guides, its kit-v* releases and check-versions --kit are removed. It stays on
    npm, deprecated. Migration: apps that used @spotcraft/kit move to @kodentuzo/spotkit.

Fixed

  • Docs: Getting started no longer mentions a Database checkbox, and the agent's API table
    lists analytics.

v0.14.1

Choose a tag to compare

@github-actions github-actions released this 22 Nov 06:12
v0.14.1
5941c2a

Changed

  • One sender per instance: MAIL_FROM is noreply@<APPS_DOMAIN> for every app, so the mail
    provider verifies one domain. Apps set their own display name. Every app may send from the
    apps domain as well as its own hosts. Without an apps domain, nothing changes.

Fixed

  • Backups to Hetzner Object Storage: requests are signed for the bucket's location (fsn1,
    nbg1 or hel1) instead of R2's auto, and the legal facts name Hetzner (Germany, or
    Finland for Helsinki) as the backups' processor.

v0.14.0

Choose a tag to compare

@github-actions github-actions released this 22 Nov 04:47
v0.14.0
20140ad

Added

  • A bundle with every release (ADR 0047):
    spotcraft-X.Y.Z.tar.gz with the server's Compose, Caddy and monitoring files and
    remote-deploy.sh, plus SHA256SUMS and a GitHub build attestation. CI also creates the
    GitHub release from this changelog.
  • The server's requirements, for running Spotcraft anywhere.

Changed

  • Spotcraft runs from an instance repository now. The recommended way is the
    kodentuzo/hetzner template, which creates the server
    and deploys the bundle of a pinned version.

Removed

  • infra/hetzner, infra/cloudflare and infra/cloud-init.yaml moved to kodentuzo/hetzner,
    with their history, as its hetzner/ and cloudflare/ roots. To migrate an existing instance:
    make a repository from the template, copy your terraform.tfvars into its roots, and move your
    local state into its remote backend with tofu init -migrate-state (its guide). The roots keep
    every resource address, so the plan afterwards shows no changes.

v0.13.0

Choose a tag to compare

@vindotski vindotski released this 22 Nov 03:55
v0.13.0
7620ead

Added

  • Instance mail (ADR 0046): a mail relay service
    that apps send through, to one provider (Lettermint first). Every app gets SMTP_URL, with its
    own name and token, and MAIL_FROM (noreply@<its public host>), and may send only from its
    own hosts. Set the new optional GitHub secret MAIL_SMTP_URL for the Deploy workflow, e.g.
    smtp://lettermint:<project API token>@smtp.lettermint.co:587; without it, the relay answers
    "try later". Apps get the new env with their next deploy.
  • The legal facts gain an email entry naming the provider, when one is set.
  • The app's Domains page shows its sender, and the SPF and DMARC records of each of its hosts
    (GET /apps/:name/mail).

Changed

  • mail is a reserved app name: the relay has it on the apps network.
  • The user pool is Spotpass now, its own repository
    (kodentuzo/spotpass) and image (vindotski/spotpass),
    moved out with its history. The auth service runs that image, pinned by digest; it behaves as
    before, with the same auth schema, env and paths. The Spotcraft image no longer contains it.
    spotcraft dev runs the same image, and SPOTPASS_DEV_IMAGE replaces SPOTCRAFT_DEV_IMAGE
    for a local build.

Spotcraft 0.12.0

Choose a tag to compare

@vindotski vindotski released this 22 Nov 02:29
v0.12.0
ac3e97d

Added

  • The API describes itself (ADR 0045): GET /openapi.json
    is the agent's API as OpenAPI 3, every route with a summary and a tag. GET /instance answers
    the version, the settings and the number of apps.
  • The API door: with API_TOKEN set (a new, optional GitHub secret for the Deploy workflow),
    clients other than the dashboard, such as Kodentuzo Studio or a script, reach the agent's API at
    /v1/* on the dashboard's domain (the dashboard).
  • Metrics through the API: GET /metrics/query and GET /metrics/query_range, read-only
    PromQL passed on to VictoriaMetrics.

Changed

  • The dashboard goes through the agent for everything: it reads metrics through the API, and
    the agent writes the uptime-probe targets. VictoriaMetrics moves to its own metrics network,
    shared only with vmagent and the agent. The dashboard's VICTORIAMETRICS_URL and PROBES_FILE
    settings are gone, and so is its probes volume. The Deploy workflow applies the new Compose
    file; nothing to do by hand.

Spotcraft 0.11.0

Choose a tag to compare

@vindotski vindotski released this 22 Nov 00:29
v0.11.0
15cd2a5

Added

  • spotcraft new <name> starts a private, local-first app from Kodentuzo's
    starter: it downloads its latest release (or --ref),
    and names it, schema included (the CLI).

Removed

  • spotcraft.dev's site (apps/site): Spotcraft's landing page and showcase are now
    kodentuzo.com/spotcraft, and spotcraft.dev redirects there
    (ADR 0044). The docs are the
    wiki, published from docs/.

Spotcraft 0.10.0

Choose a tag to compare

@vindotski vindotski released this 21 Nov 21:42
v0.10.0
48a6eb9

Removed

  • Spotcraft no longer adds the analytics script to apps' pages
    (ADR 0043). Caddy changes no app's content now,
    only its headers, and runs the official binary without the replace-response module.
    /_spotcraft/s.js, /_spotcraft/e and /_spotcraft/config.json stay.

  • /_spotcraft/privacy is gone. Each app says what is counted in its own privacy policy,
    and offers the switch in its own pages.

    Migration: before you update, every web app that should keep counting visits loads the
    tracker itself:

    1. Install @kodentuzo/spotkit 0.2.0 or later, and call analytics() from
      @kodentuzo/spotkit/client once in the browser. It follows ANALYTICS_MODE, and adds
      nothing a second time if the script is already on the page, so it can ship before this
      release. Without a package, add
      <script defer src="/_spotcraft/s.js" data-website-id="…"></script> with the id from
      /_spotcraft/config.json, in opt-out mode only.
    2. In opt-out mode, show a switch that turns counting off (Spotstrap's analytics-switch
      block), and in opt-in mode, ask first (analytics-prompt).
    3. Remove links to /_spotcraft/privacy.

v0.9.1

Choose a tag to compare

@vindotski vindotski released this 21 Nov 17:00
v0.9.1
b8e8402

Fixed

  • Deploys failed on 0.9.0, and the legal facts weren't served. The agent kept the facts'
    date in /opt/spotcraft/legal.json, but its container can only write apps/ and sites/.
    Building the facts then failed, which failed every deploy (they give apps LEGAL_FACTS)
    and the agent's rewrite of every site at start. The file is now apps/.legal.json, and a
    date that can't be saved is logged instead of failing a deploy or a site. The agent also
    lists only folders in apps/ as apps.

v0.9.0

Choose a tag to compare

@vindotski vindotski released this 21 Nov 16:26
v0.9.0
3f433b2

Added

  • Guests can export and delete their data (ADR 0043).
    GET /_spotcraft/auth/export answers what the pool holds about the signed-in user as JSON,
    without tokens or hashes. Self-delete (POST /_spotcraft/auth/delete-anonymous-user, Better
    Auth's) is now documented in the contract; it cascades through every app.
  • The pool forgets what it no longer needs, once a day: expired sessions are deleted, and a
    session's IP address and user agent are cleared after 30 days unused (AUTH_IP_DAYS).
  • Every deleted user's id is logged in auth.deletions for as long as backups are kept
    (AUTH_BACKUP_DAYS, 30 days), so a restore can delete them again. A trigger fills it, so the
    dashboard's deletes and the idle-guest cleanup count too.
  • Restore an app from a backup in the dashboard (the app's Backups page). The agent backs
    up the data now, restores the app's schema in one transaction as the app's own role, then
    deploys it again. Users deleted since the backup stay deleted: the agent puts them back as
    placeholders for the restore, then deletes them with their rows. If it fails, the data is as
    it was. The agent's routes are GET /apps/:name/backups and POST /apps/:name/restore.
  • Legal facts for every app (ADR 0043). On the
    dashboard's Settings page, Privacy and legal takes who runs the apps (name, postal
    address, email, supervisory authority, hosting provider). The agent adds what the instance
    does with personal data, each with its purpose, legal basis, retention, processor and any
    transfer outside the EU. Apps get the facts as LEGAL_FACTS and at
    /_spotcraft/legal.json, for their privacy policy and legal notice; saving deploys every app
    again. The page also lists what the owner still does, and downloads the facts as the record
    of processing. spotcraft dev writes example facts.
  • Three analytics modes (ANALYTICS_MODE, ADR 0043),
    since consent rules differ between EU countries: opt-out (the default, as before), opt-in
    (nothing added to pages; apps load the tracker after the visitor agrees) and server (nothing
    in the browser; only requests and accounts are counted). config.json says the mode, the
    legal facts follow it (consent for opt-in, no analytics entry for server), and the
    dashboard's Settings shows it.
  • Old analytics are deleted: Umami keeps events forever, so the agent deletes those older
    than ANALYTICS_DAYS (395) every night. The legal facts now say so.
  • A guide for when personal data leaks (docs/guides/breach.md).
  • The pool's retention settings are in the server's Compose file and .env.example:
    AUTH_GUEST_DAYS, AUTH_IP_DAYS, AUTH_BACKUP_DAYS.

Changed

  • LEGAL_FACTS is a reserved env name (breaking, unlikely to matter): Spotcraft sets it for
    every container app, so an app's own env can't. To upgrade, rename an env variable of that
    name in any app first.
  • Umami's events older than ANALYTICS_DAYS (395) are deleted every night from this
    version on. To keep older ones, set ANALYTICS_DAYS higher in the server's .env before
    deploying.
  • The agent reads AUTH_GUEST_DAYS, AUTH_IP_DAYS and AUTH_BACKUP_DAYS too, for the legal
    facts; Compose passes the same values to it and to the pool.
  • /_spotcraft/config.json carries the analytics mode, and /_spotcraft/privacy says
    what each mode counts.
  • One long-lived branch, main (ADR 0042): releases
    are tags, and the website updates from them.
  • Server images: Umami 3.5.0 (also in the local stack), node-exporter 1.13.1 and cAdvisor
    0.61.1.