Evaluate the product
Use /app to review the UI and operating model before deployment planning.
This guide covers the self-hosted deployment path for Mermaduckle. A live product
environment is available at /app for evaluation, while customer
deployments can run in Fly or other infrastructure with either self-managed or
supported rollout.
Mermaduckle supports live evaluation, self-hosted deployment, and managed rollout.
Use /app to review the UI and operating model before deployment planning.
Use this guide to run the same service in Fly or your preferred infrastructure stack.
Use a supported rollout when implementation speed and operating help are the priority.
Run a local instance from the repository root and open the product in the browser.
cargo run -p mermaduckle-server
//app/docs/api/healthThe repository already includes the deployment artifacts required for a Fly rollout.
flyctl deploy -a <app-name> --remote-only --config fly.toml
The current repository configuration uses app = "mermaduckle" and serves
the application on internal port 3001.
Use an app-scoped deploy token to ship to Fly automatically on pushes to main.
fly tokens create deploy --app <app-name>
FLY_API_TOKEN..github/workflows/fly-deploy.yml.flyctl deploy --remote-only --config fly.toml.Use the included PowerShell helper when you want to release from your own machine.
pwsh -File tools/deploy_fly.ps1 -AppName mermaduckle -RemoteOnly
Add -BuildOnly if you want to build and push the image without releasing it immediately.
Use these Fly commands when configuring a production domain and managed TLS.
flyctl domains add mermaduckle.com -a <app-name>
flyctl ips allocate-v4 -a <app-name>
flyctl certs create mermaduckle.com -a <app-name>
These values are read by the server at runtime.
data/app.dbhttp://localhost:114340.0.0.03001These are the key files involved in a Fly deployment and production rollout.
deploy/Dockerfile.flyfly.tomldocs/deploy/fly.md.github/workflows/fly-deploy.ymltools/deploy_fly.ps1README.md