phoenix-ops

To deploy a Phoenix application, you prepare assets with `mix assets.deploy`, then build a production release using `MIX_ENV=prod mix release`. This creates a self-contained artifact for deployment.

The best way to configure Phoenix applications at runtime is by using environment variables and the `config/runtime.exs` file. This allows dynamic configuration when the application starts in production.

You can set up clustering for Phoenix PubSub and Presence using `libcluster`. This enables multi-node communication and distributed systems on the BEAM for real-time features.

Yes, Phoenix deployment works with containers, systemd, and cloud platforms. The deployment process addresses common patterns across these environments, including endpoint hardening and health checks.

You integrate telemetry and logging in a Phoenix production release by configuring observability tools within your deployment. This provides robust monitoring and health checks for the running application.