Elixir/Phoenix deployment patterns — Dockerfile, fly.toml; Use when configuring.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Elixir/Phoenix Deployment Reference
Quick reference for deploying Elixir/Phoenix applications.
## Iron Laws — Never Violate These
1. **Config at runtime, not compile time** — Secrets in `config.exs` get baked into the release binary. Use `runtime.exs` with env vars so secrets are resolved at boot
2. **Graceful shutdown ≥ 60 seconds** — Shorter timeouts kill in-flight requests and WebSocket connections mid-operation, causing data loss for users
3. **Health checks required** — Without startup/liveness/readiness endpoints, orchestrators can't distinguish a booting node from a dead one, leading to cascading restarts
4. **SSL verification for database** — Skipping `verify: :verify_peer` allows MITM attacks between your app and database; production data traverses the connection
5. **No CPU limits** — The BEAM scheduler assumes it owns all cores; cgroups CPU limits cause scheduler collapse where the VM thinks it has more cores than it can use, leading to latency spikes
6. **Guard optional service credentials** — `runtime.exs` runs whenever a
release boots, including `eval`-based migration commands. Only require S3,
…
The line at the top of this page pins the label git:20260724.8ff2e3c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_g5hxnpfj35z7b5k3
GET https://markdownregistry.com/api/v1/resolve?ref=oliver-kriska/claude-elixir-phoenix/deploy
GET https://markdownregistry.com/api/v1/blob/d879b859931e0dd18a660e5d8ed57a852d95e939bfdbe0725c7839c844188b43
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
oliver-kriska/claude-elixir-phoenix · .claude/skills/cc-changelog/SKILL.md · CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check,
analyze impact on plugin (breaking…
oliver-kriska/claude-elixir-phoenix · .claude/skills/plugin-dev-workflow/SKILL.md · Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying…
oliver-kriska/claude-elixir-phoenix · .claude/skills/promote/SKILL.md · Generate X/Twitter release promotion posts with ASCII tables and CodeSnap rendering. Use when writing release posts…
pedrohcgs/claude-code-my-workflow · .claude/skills/deploy/SKILL.md · Render Quarto `.qmd` slides to HTML and sync to `docs/` for GitHub Pages. Use when user says "deploy", "publish the…
microsoft/power-platform-skills · plugins/code-apps/skills/deploy/SKILL.md · Builds and deploys a Power Apps code app to Power Platform. Use when deploying changes, redeploying an existing app, or…
microsoft/power-platform-skills · plugins/mobile-apps/skills/deploy/SKILL.md · Use to deploy, publish, or push an Expo/React Native Power Apps mobile app to a Power Platform tenant.
