phoenix-ops

Manage Elixir Phoenix releases, runtime configuration, clustering, and production hardening on the BEAM.

68|19|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill phoenix-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phoenix-ops
Source: https://github.com/bobmatnyc/claude-mpm-skills/tree/main/toolchains/elixir/ops/phoenix-ops
Command: npx skills add https://github.com/bobmatnyc/claude-mpm-skills --skill phoenix-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the complex process of deploying Elixir Phoenix applications to production, ensuring robust operations, secure configurations, and efficient resource management on the BEAM.

Core Features & Use Cases

  • Production Releases: Manages the creation and deployment of Elixir releases for Phoenix applications.
  • Runtime Configuration: Configures applications using environment variables and runtime.exs for dynamic settings.
  • Clustering & PubSub: Sets up node discovery and distributed PubSub/Presence for scalable applications.
  • Security & Hardening: Implements HTTPS, secure cookies, CORS, and secrets management.
  • Observability: Integrates telemetry, logging, and health checks for monitoring.
  • Use Case: Deploying a Phoenix application that requires real-time updates and needs to scale across multiple servers, ensuring all nodes can communicate and share state securely.

Quick Start

Prepare your Phoenix application for production by running mix assets.deploy and then mix release with the appropriate environment variables set.

Frequently Asked Questions about phoenix-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Phoenix application to production using Elixir releases?

Deploy a Phoenix application by running `mix assets.deploy` followed by `mix release` with the appropriate environment variables set. This process generates a self-contained Elixir release for production delivery.

How does runtime configuration work in Elixir Phoenix deployments?

Runtime configuration in Phoenix deployments uses environment variables and `runtime.exs` to inject dynamic settings at boot time. This allows a single release artifact to adapt to different deployment targets without recompilation.

What's the best way to set up clustering for multi-node Phoenix applications?

Set up clustering for multi-node Phoenix applications using libcluster for node discovery, enabling distributed PubSub and Presence across servers so all nodes can communicate and share state securely.

Can I use environment variables for secrets management in Phoenix production releases?

Yes, environment variables are used for secrets management in Phoenix production releases. They are referenced within `runtime.exs` to securely inject sensitive data and configure endpoints at runtime.

How do I add telemetry and health checks to a Phoenix application for production observability?

Add production observability to a Phoenix application by integrating telemetry, logging, and health checks. This monitors application metrics and ensures operational visibility across deployed nodes.

What production hardening steps are needed for Phoenix endpoints?

Production hardening for Phoenix endpoints involves implementing HTTPS, secure cookies, and CORS. These security measures ensure secure application delivery and protect the BEAM deployment.