发行Erlang的最佳实践是什么？ [英] What are best practices for making Erlang releases?

问题描述

我一直在检查Faxien + Sinan和Rebar，而Erlang OTP的基本原理似乎是在单个Erlang映像实例上安装应用程序和发行版。使发布保持自我控制的最佳实践是什么？有没有办法打包发布版本，而不必为要部署到的计算机修改站点？怎么样将所有依赖项收集到代码库中进行管理？

I've been checking out Faxien+Sinan and Rebar, and the basic philosophy of Erlang OTP seems to be, install applications and releases on a single Erlang image instance. What are the best practices for keeping releases self contained? Is there a way to package releases such that you don't have to modify the site for machines that you're deploying to? How about gathering all dependencies into the codebase for management?

也许我不赞成这样做……我来自Java背景并且无所不包已安装，但JVM似乎非常不同。

Perhaps I'm going against the grain... I come from a Java background and the philosophy of "nothing pre-installed but the JVM" seems very different.

推荐答案

恕我直言，这不能用几句话来回答。您应该阅读其中包含的文档的某些部分，尤其是 Erlang / OTP系统文档（otp-system-documentation-XYZpdf，其中XYZ为版本号），或者看看这本书 Erlang和OTP的实际应用，因为在本书中，从一开始就使用Erlang / OTP概念并最终构建了一个服务示例，其中的服务具有不同的部分

IMHO this can't be answered in a few sentences. You should have to read some parts of the included documentation, especially "Erlang/OTP System Documentation" (otp-system-documentation-X.Y.Z.pdf, with X.Y.Z being the version number), or have a look at the book "Erlang and OTP in Action" because throughout this book there is "one" example of a "service" with different "parts" from the first steps, using Erlang/OTP concepts and finally building a "release".

恕我直言，这是目前最好的书，因为它不仅介绍了Erlang，而且还介绍了什么是OTP以及如何在项目中使用OTP。 。它不仅是一些松散的样本，而且所有内容都围绕一个项目构建。

IMHO this is currently the best book around, because it not only introduces Erlang, but also shows what OTP is and how OTP is used for a project. And it is not just a collection of loose samples, but everything is build around a single project.

这篇关于发行Erlang的最佳实践是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！