Elixir & Phoenix: Scalable Backend Development · レッスン

Mix Releaseによるリリースの構築

「mix release」を使って、単体で動作しデプロイ可能なElixirアプリケーションのリリースを作成します。

「Mix Releaseによるリリースの構築」はCoddyKit上の無料Elixir & Phoenix: Scalable Backend Developmentレッスンです。これはレッスン1/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応のAIチューターでハンズオン演習できます。これはElixir & Phoenix: Scalable Backend Development学習パスの一部であり、ウェブとCoddyKitアプリ全体で進捗が同期されます。 Elixir & Phoenix: Scalable Backend Developmentコースには全4レッスンが含まれています。

このレッスンの一部はまだ翻訳されておらず、英語で表示されています。

Welcome to Elixir Releases

When you develop an Elixir application, you often run it with mix run --no-halt. This is great for development, but not ideal for production.

For deployment, we need a self-contained package that can run independently, without needing the Mix build tool or even Elixir's source code on the target machine. This is where releases come in!

Why `mix run` Isn't Enough

Running an application with mix run has a few drawbacks for production:

It requires the full Mix build tool and your project's source code.
It uses the development environment configuration by default.
Startup can be slower as it needs to compile and load dependencies.
It lacks proper daemonization features for background processes.

Introducing `mix release`

mix release creates an OTP release. Think of it as a complete, self-contained package of your Elixir application and its dependencies.

It includes the Erlang VM, your compiled code, and all necessary scripts to start, stop, and manage your application as a standalone service.

Benefits of Using Releases

Using releases offers several key advantages:

Self-contained: No need for Mix or Elixir installation on the server.
Faster Startup: Pre-compiled and optimized for production.
Production-ready: Designed for daemonization and supervision.
Hot Code Swapping: Supports upgrading running systems without downtime (advanced).

Generating Your First Release

To create a release, first ensure your project has a supervisor. Most Phoenix projects and projects created with mix new my_app --sup already have one.

Then, simply run the mix release command. This will compile your project and its dependencies for the production environment.

mix new my_release_app --sup
cd my_release_app
mix deps.get
mix release

Exploring the Release Structure

After running mix release, you'll find your release in _build/prod/rel/your_app_name/.

Inside, you'll see a bin directory containing a script to manage your app, lib with all compiled dependencies, and releases with version-specific files.

my_release_app/
├── _build/
│   └── prod/
│       └── rel/
│           └── my_release_app/
│               ├── bin/
│               │   └── my_release_app (start/stop script)
│               ├── lib/
│               ├── releases/
│               └── erts-...
├── config/
├── lib/
└── mix.exs

Running Your Released Application

To start your application from a release, use the generated script in the bin directory. You can start it in the foreground or as a daemon.

For a production environment, you'd typically start it in the background.

# Start in foreground (for testing)
_build/prod/rel/my_release_app/bin/my_release_app start_iex

# Start as daemon (production)
_build/prod/rel/my_release_app/bin/my_release_app start

# Stop a running daemon
_build/prod/rel/my_release_app/bin/my_release_app stop

Runtime Configuration with `runtime.exs`

For production deployments, you often need to configure your application based on its environment (e.g., database credentials, API keys).

mix release uses config/runtime.exs, which is executed after the release is built and before the application starts. This is perfect for reading environment variables.

# config/runtime.exs
import Config

config :my_release_app, 
  database_url: System.get_env("DATABASE_URL"),
  api_key: System.get_env("API_KEY")

Upgrades and Downgrades (Advanced)

One of the most powerful features of OTP releases is the ability to perform hot code upgrades. This means you can update your running application with new code without stopping it, leading to zero downtime deployments.

While this is an advanced topic, `mix release` lays the groundwork for it by packaging your application in a way that allows for version management and patching.

Release Benefits Check

Which of the following are key benefits of using mix release for deploying an Elixir application?

Recap: Ready for Deployment!

You've learned that mix release is the standard way to package Elixir applications for production. It creates a self-contained, optimized bundle, independent of the Mix toolchain.

Releases offer faster startup, robust daemonization, and support for advanced features like hot code upgrades. Coupled with config/runtime.exs, they provide a powerful and flexible deployment solution.

よくある質問

「Mix Releaseによるリリースの構築」レッスンは無料ですか？

はい。「Mix Releaseによるリリースの構築」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、Elixir & Phoenix: Scalable Backend Developmentコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Elixir & Phoenix: Scalable Backend Developmentコースには全4レッスンが含まれています。

「Mix Releaseによるリリースの構築」で何を学びますか？

「mix release」を使って、単体で動作しデプロイ可能なElixirアプリケーションのリリースを作成します。ブラウザで直接実行するハンズオンコードでElixir & Phoenix: Scalable Backend Developmentを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Elixir & Phoenix: Scalable Backend Developmentを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのElixir & Phoenix: Scalable Backend Developmentは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン1/4です。

「Mix Releaseによるリリースの構築」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このElixir & Phoenix: Scalable Backend Developmentレッスンでコードを書いて実行できますか？

はい。すべてのElixir & Phoenix: Scalable Backend Developmentレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Elixir & Phoenix: Scalable Backend Developmentに戻る