fly.toml is a Fly.io app config. fly launch --from creates an app from it: one
Machine runs the published image ghcr.io/the-40-thieves/reliquary-tc:latest with a volume mounted at
/data. The image’s ENTRYPOINT boots the server from RELIQUARY_TC_CONFIG, which the deploy copies in
from the repository, and the server serves HTTP on port 8765.
The app uses the image rather than building the repository’s Dockerfile, so the release that CI
tested is the one that runs, and Fly runs no build.
What fly.toml sets
/healthz is unauthenticated liveness only, so the check needs no token.
Cost
As listed on Fly.io’s pricing page on 2026-10-19, for Ashburn (iad) and Secaucus (ewr), the lowest-priced regions:
That is about $14.20 per month for the app as written. Prices vary by region and change, so check the
pricing page before you create the app. New organizations have no free tier, only a trial. A volume
is billed whether or not the Machine runs.
Create the app
-
Run the launch command from a checkout or an empty directory:
--fromuses the repository as a template,--copy-configkeeps itsfly.tomlwithout prompting, and--no-deploystops before the first deploy. Pick the app name and the region when asked.fly launchwrites the app name intofly.toml. -
Set the public URL and the JWT secret as secrets.
--stagestores them without deploying:The public URL is not secret. It is set as a secret so thatfly.tomlstays the same for every app. The JWT secret must be at least 32 characters;openssl rand -hex 32gives 64. -
Deploy:
With a volume mounted, Fly creates one Machine, not the usual two, because volumes are not replicated between Machines. See Fly’s app availability notes.
-
Seed the vault (see Vault source) and mint a client token inside the
Machine:
--user bunruns the command as the image’s unprivilegedbunuser (uid 1000), which is the user the server runs as. The default user offly ssh consoleis root, so without the flag the command could leave root-owned files under/data, which the server cannot write to. That default is not re-checked on a live app here. Send the printed token asAuthorization: Bearer <token>tohttps://<app>.fly.dev/mcp. Add only the scopes that client needs.
Public URL and custom domain
RELIQUARY_TC_PUBLIC_URL must be https://host or https://host:port, with no path, query or
credentials. Fly gives each app a https://<app>.fly.dev address; set the secret to that origin, or to
your own domain once it is attached to the app. The value sets auth.resource (the origin plus /mcp)
and is added to allowedHosts, so a custom domain must be attached and resolve before clients connect.
After any change of domain, set the secret again and deploy.
Changing the config
The config file comes fromdeploy/config/reliquary-tc.config.json in the directory fly deploy runs
from, and is copied in at deploy time. To change it, edit that file and run fly deploy. For example, to
use the openai embeddings provider, name it in the file and set OPENAI_API_KEY with fly secrets set.
See Embeddings.
To use the bundled authorization server instead of minted tokens, see
Railway’s Authentication section. The config then needs
auth.as.issuer, which the shared file does not set.
Region and vault source
A volume lives on one server in one region, so the Machine stays in that region. Pick the region near your clients. Fly takes daily snapshots of a volume and keeps them for 5 days by default; the retention can be set withsnapshot_retention in [mounts].
A new volume mounted over /data hides the /data/vault directory the image creates. Because
RELIQUARY_TC_VAULT_PATH names it, the server creates the empty vault directory (mode 0750) at first
boot instead of exiting.
The volume is the only copy of the vault that the server reads. To keep the vault in step with a Git
repository, use the -git image and the variables in
Git-backed vault. Those tags are first published with
the next release, so the -git image is not yet available for [build] image.
What this does not do yet
- Not yet verified on a live Fly app. The fields were checked against Fly’s documentation, not by creating an app. A live deploy check is still needed.
- Volume ownership (likely fine, unverified). A reviewer found that Fly chowns a new volume’s mount to
the image’s USER, so a permission error on
/datais not the expected failure. No live app has confirmed this. - Health check Host header (unverified). The
Host: localhostoverride is set infly.toml, and the server’s guard acceptslocalhost, but no live check has been observed sending that header or passing. [[files]]underfly launch --from(unverified).fly launch --fromclones the repository, and thelocal_pathis taken relative to the clonedfly.toml. That has not been observed on a live app.- No deploy button. Fly has no button equivalent to Render’s, so the README has no link for it.