创建 Erlang 发布包
使用 rebar3 和 relx 等工具，将 Erlang 应用、依赖项和 Erlang 运行时打包成自包含的发布包。
创建 Erlang 发布包 是 CoddyKit 上的免费 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 课时。 这是第 1 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
What are Erlang Releases?
When you develop an Erlang application, it's a collection of modules and configuration files. To deploy it, you need to package it all up.
An Erlang Release is a self-contained, deployable package of your application, its dependencies, and optionally, a specific version of the Erlang Runtime System (ERTS).
- It's like a standalone executable for your Erlang system.
- It simplifies deployment by bundling everything needed to run.
Benefits of a Release
Why go through the effort of creating a release? Releases offer significant advantages for production systems:
- Self-contained: Includes all necessary Erlang libraries and even the Erlang VM itself.
- Simplified Deployment: Just copy the release folder to a server and start it.
- Version Management: Each release has a clear version number, making upgrades and rollbacks easier.
- Foundation for Live Upgrades: Releases are essential for Erlang's famous 'hot code loading' feature (covered in a later lesson!).
Meet rebar3
Building Erlang applications and releases manually can be complex. Fortunately, we have rebar3!
rebar3 is the standard build tool for Erlang. It handles:
- Project creation and management
- Dependency resolution
- Compilation
- Testing
- And, crucially for this lesson, creating releases.
It streamlines the entire development and deployment workflow.
Your Erlang Application Code
Let's start with a very simple Erlang module. In a real application, this would be part of your overall system logic.
For demonstration, we'll create a module with a main/0 function, which can be run directly. This module will be included in our release.
-module(my_release_app).
-export([main/0]).
main() ->
io:format("Hello from my Erlang release application!~n").The Application Resource File
Every Erlang application has an application resource file (.app or .app.src). This file defines metadata about your application, such as its version, description, and which modules it depends on.
rebar3 uses the .app.src file to generate the final .app file during the build process.
{application, my_release_app,
[{description, "My simple release app"},
{vsn, "0.1.0"},
{registered, []},
{applications, [
kernel,
stdlib
]},
{mod, {my_release_app, []}},
{env, []}
]}.Configuring the Release
To tell rebar3 how to build your release, you add a relx section to your rebar.config file. This configuration specifies:
- The name and version of your release.
- Which applications to include.
- If the Erlang Runtime System (ERTS) should be bundled.
For development, we often don't include ERTS to save space.
{apps, [my_release_app]}.
{relx, [{release, {my_release_app, "0.1.0"}, [my_release_app]},
{dev_mode, true},
{include_erts, false},
{extended_start_script, true}]}.Building Your Release Bundle
With your application code, .app.src, and rebar.config in place, building the release is straightforward. rebar3 will compile your code, fetch dependencies, and package everything into a single directory.
This command does all the heavy lifting:
rebar3 releaseInside the Release Package
After running rebar3 release, you'll find your release in _build/default/rel/my_release_app/. The structure typically includes:
- bin/: Contains the start script for your application.
- lib/: All your application's compiled code and dependencies.
- releases/: Release definitions and version information.
- erts/: (Optional) The Erlang Runtime System if
include_ertswas true.
This organized structure makes deployment predictable and reliable.
Running Your Packaged App
Once built, you can start your Erlang application by executing the generated start script. This script handles starting the Erlang VM and loading your application.
Navigate to the release directory and use the bin/<release_name> script.
For our example, you would run (in a shell, not runnable in this environment):
_build/default/rel/my_release_app/bin/my_release_app startRelease Benefits Check
Creating an Erlang release is a crucial step for deployment. Which of the following are primary benefits of packaging an Erlang application as a release?
Recap: Erlang Releases
You've taken a big step towards deploying Erlang applications!
- Erlang Releases package your app, its dependencies, and optionally ERTS.
- rebar3 is the essential tool for building and managing releases.
- The
.app.srcandrebar.configfiles define your application and release. - Releases simplify deployment, versioning, and enable powerful features like live upgrades.
Next, we'll dive into the fascinating world of hot code loading and how to perform live upgrades on running systems!
用 AI 导师学习 Erlang — 免费
在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。
- 课程
- 12
- 课程
- 48
常见问题解答
「创建 Erlang 发布包」课时是免费的吗？
是的 — 「创建 Erlang 发布包」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 课程的其余内容，请升级到 CoddyKit PRO。 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 课程共包含 4 节课。
「创建 Erlang 发布包」这节课中我会学到什么？
使用 rebar3 和 relx 等工具，将 Erlang 应用、依赖项和 Erlang 运行时打包成自包含的发布包。 你通过在浏览器中直接运行的动手代码来练习 Erlang OTP: Distributed & Fault-Tolerant Systems Programming，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 1 节课，共 4 节。
「创建 Erlang 发布包」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 课中编写并运行代码吗？
能。每节 Erlang OTP: Distributed & Fault-Tolerant Systems Programming 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。