ShippedElixir hosting
on Shipped.
Bring your Elixir application and its supervision structure to a running service. Shipped handles the infrastructure outside your application.
Deploy a release built for production
Package your Elixir application as a release with the runtime and system dependencies it needs. A container keeps that environment explicit. Run an HTTP application as a web service or choose a worker for background processing, preserving the application and supervision structure you designed in Elixir.
Read environment settings at the right time
Elixir distinguishes build-time and runtime configuration. Keep deployment-specific credentials and connection strings in runtime configuration backed by secrets. This lets the same release connect to different resources in staging and production without baking private values or one environment’s database address into the compiled application.
Keep durable work outside process memory
Supervised processes help an application manage execution, but restarting a process does not restore arbitrary in-memory records. Use PostgreSQL or another durable service for persistent data and job progress. Logs help trace behavior after deployment, and a separate worker gives background work its own operational role.
A little more detail
Questions about Elixir?
Does an Elixir release need Mix on the running server?
A properly assembled release packages the compiled application and its required runtime components. Include the release’s remaining operating-system dependencies in the deployment image.
Does Shipped automatically create an Erlang cluster?
Application clustering is a separate design and configuration decision. Do not assume deploying multiple instances automatically establishes the discovery, distribution, and state-sharing behavior your app requires.
Phoenix
Ship Phoenix applications on Shipped with an Elixir release, PostgreSQL, private endpoint settings, and persistent application storage.
Explore PhoenixBackground workers
Run background workers on Shipped for queues, imports, notifications, and long-running application tasks, with separate resources and deployment history.
Explore Background workersSecrets
Manage application secrets in Shipped, connect them to the right services and environments, and keep credentials out of Git and frontend bundles.
Explore Secrets
Docker
Deploy containerized applications on Shipped with your runtime and system dependencies, connected services, domains, secrets, and rollbacks.
Explore DockerFrom your workspace to the web