Managoat

Managoat is the hosted Fountain. Fountain is the open-source engine, and its name is on the CLI, the API, the SDK and this manual. Everything here applies to Managoat unless a page says it is for a self-hosted server.

Run a release task

This guide shows you how to run an operator action that touches data. Each one of them uses the same pattern.

The pattern

Compose:

docker compose exec app bin/fountain_server eval \

  'Fountain.Release.verify_email("[email protected]")'

Kubernetes:

kubectl exec -n fountain deploy/fountain -- \

  sh -c "PHX_SERVER=false bin/fountain_server eval 'Fountain.Release.verify_email(\"[email protected]\")'"

eval starts the database connection and nothing else. It never starts the app. So a task cannot compete with the live server for ports, for background jobs, or for conversation processes.

PHX_SERVER=false says that out loud in a container that sets it true. Include it, and the pattern is always safe to paste.

The tasks

Task What it does
Fountain.Release.verify_email("[email protected]") Marks an account's email verified, and sends nothing. It is the escape hatch for a mail provider that broke. Since ADR 0011, EMAIL_DELIVERY=none self-verifies at registration.
Fountain.Release.promote_admin("[email protected]") Grants the admin role. The admin audit trail records it under a system actor. It is the manual alternative to FIRST_USER_ADMIN=true (ADR 0011).
Fountain.Release.rebuild_credit_lots() Replays every credit ledger and rewrites the lots. Safe to rerun.
Fountain.Release.backfill_turn_replies() Fills the reply column on each turn that closed before the column existed. Safe to rerun.
Fountain.Release.migrate() Runs the migrations that are due, by hand. It is what bin/migrate runs. They already run at each boot, unless MIGRATE_ON_BOOT=false. In that case this, in a Job before the rollout, is how they run at all. That switch never skips it.
Fountain.Release.rollback(Fountain.Repo, version) Rolls migrations back to a version. It is a last resort. Read Upgrade an instance first.

Warnings

Use rollback/2 to reverse one migration that you understand. Do not attempt to reverse a whole release's migrations on production data.