Pemberian Versi dan Penerapan Rilis
Pahami praktik terbaik untuk memberi versi pada rilis, menerapkan pembaruan, dan mengelola pengembalian dalam lingkungan produksi
Pemberian Versi dan Penerapan Rilis adalah pelajaran Erlang OTP: Distributed & Fault-Tolerant Systems Programming gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Erlang OTP: Distributed & Fault-Tolerant Systems Programming, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Erlang OTP: Distributed & Fault-Tolerant Systems Programming mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
Why Version Your Releases?
When you build an Erlang application for production, it's bundled into a release. Just like any software, releases need clear version numbers.
Versioning helps you:
- Track changes over time.
- Identify specific builds.
- Manage compatibility with other systems.
- Plan for upgrades and rollbacks.
Erlang's Versioning System
In Erlang, versioning happens at different levels. Each individual application (an .app file) has its own version. The overall release (the .rel file) also has a version that typically reflects the entire bundle.
The vsn key in an .app file defines an application's version.
% my_app.app file (conceptual)
{application, my_app,
[{description, "My Erlang Application"},
{vsn, "1.0.0"},
{modules, [my_app_app, my_app_sup]},
{registered, []},
{applications, [kernel, stdlib]},
{mod, {my_app_app, []}},
{env, []}]}.Semantic Versioning (SemVer)
A widely adopted standard is Semantic Versioning (SemVer), typically formatted as MAJOR.MINOR.PATCH. It's a great practice to follow for your Erlang applications.
- MAJOR: Incremented for incompatible API changes.
- MINOR: Incremented for new functionality in a backward-compatible way.
- PATCH: Incremented for backward-compatible bug fixes.
This helps users understand the impact of an upgrade.
Applying SemVer in Erlang
You'll typically apply SemVer to your application's vsn in the .app file. When you create a release, its version (relvsn) often matches the main application's version or follows a similar scheme.
Tools like rebar3 manage these versions when building releases.
% my_app.app file
{application, my_app,
[{description, "My Erlang Service"},
{vsn, "1.2.3"},
{modules, [my_app_app, my_app_sup]},
{registered, []},
{applications, [kernel, stdlib]},
{mod, {my_app_app, []}},
{env, []}]}.Deployment Strategies Overview
Once you have a versioned Erlang release, how do you get it running in production? There are several strategies, depending on your system's requirements for uptime and complexity.
- Cold Deployment: Simplest, involves downtime.
- Hot Upgrades: Zero-downtime (covered in previous lesson).
- Blue/Green or Canary Deployments: More advanced, often used with orchestration tools.
Cold Deployment: Simple Restart
A cold deployment is the most straightforward method. You stop your currently running Erlang system completely, replace its files with the new release, and then start the new version.
This method always incurs downtime, making it suitable for systems where brief interruptions are acceptable.
# Stop the old release
/path/to/my_app/bin/my_app stop
# (Replace files with new release)
# Start the new release
/path/to/my_app/bin/my_app startHot Upgrades vs. Full Deployment
Recall from the previous lesson that hot code loading allows you to upgrade a running Erlang system without stopping it.
While powerful for applying patches or minor feature additions, hot upgrades are specific to changing *parts* of a running system. A full deployment often refers to the initial setup or a complete replacement of the entire release, sometimes involving a cold restart or more advanced traffic management.
The Importance of Rollbacks
Even with careful testing, new deployments can introduce unexpected issues. A robust deployment strategy always includes a plan for rollbacks.
A rollback means reverting your system to a previous, stable version if the new deployment fails or causes problems. This minimizes the impact of failures and restores service quickly.
Erlang's Rollback Mechanism
Erlang releases are designed to support rollbacks. When you perform a hot upgrade, Erlang generates an .relup script that describes how to move between versions. Crucially, it also knows how to reverse that script to go back.
Even with cold deployments, you can switch back to a previous release by managing your release directories and restarting the desired version.
# Example of a rollback command using release_handler
# This would typically be part of a custom script or release tool
% release_handler:install_release("my_app-1.1.0").
% release_handler:make_permanent("my_app-1.1.0").
# Alternatively, for cold deployment:
# /path/to/my_app_1.1.0/bin/my_app startTest Your Understanding
Order the steps for a typical cold deployment of an Erlang release.
Summary: Versioning & Deployment
You've learned about the critical aspects of release versioning and deployment in Erlang:
- Versioning: Use
vsnin.appfiles, ideally following SemVer (MAJOR.MINOR.PATCH), to track and manage changes. - Deployment: Understand cold deployment (with downtime) and its distinction from hot upgrades.
- Rollbacks: Always plan for reverting to a stable previous version to ensure system resilience.
These practices are key to managing robust Erlang applications in production!
Belajar Erlang dengan tutor AI — gratis
Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.
- Kursus
- 12
- Pelajaran
- 48
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pemberian Versi dan Penerapan Rilis” gratis?
Ya — teks lengkap “Pemberian Versi dan Penerapan Rilis” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Erlang OTP: Distributed & Fault-Tolerant Systems Programming, upgrade ke CoddyKit PRO. Kursus Erlang OTP: Distributed & Fault-Tolerant Systems Programming mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Pemberian Versi dan Penerapan Rilis”?
Pahami praktik terbaik untuk memberi versi pada rilis, menerapkan pembaruan, dan mengelola pengembalian dalam lingkungan produksi Kamu berlatih Erlang OTP: Distributed & Fault-Tolerant Systems Programming dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Erlang OTP: Distributed & Fault-Tolerant Systems Programming?
Tidak diperlukan pengalaman sebelumnya. Erlang OTP: Distributed & Fault-Tolerant Systems Programming di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.
Berapa lama pelajaran “Pemberian Versi dan Penerapan Rilis” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Erlang OTP: Distributed & Fault-Tolerant Systems Programming ini?
Ya. Setiap pelajaran Erlang OTP: Distributed & Fault-Tolerant Systems Programming menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Membuat Rilis Erlang
- Pemuatan dan Pemutakhiran Kode Langsung
- Pemberian Versi dan Penerapan Rilis
- Konfigurasi Rilis & Skrip Boot