二郎发布的最佳实践？ [英] Erlang Release Best Practices?

问题描述

我是一个Erlang小白，我已经检查出Faxien +思南和钢筋，和Erlang OTP的基本理念似乎是，在一个Erlang的图像实例上安装的应用程序和发布。什么是自包含保持释放的最佳做法？有没有一种方法来包装版本，这样你就不必修改你正在部署到机器的网站？如何收集所有的依赖到codeBase的管理？

I'm an Erlang noob, and 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的背景和无pre-安装，但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.

推荐答案

恕我直言，这不能用几句话来回答。你应该阅读文档包含的某些部分，尤其是二郎山/ OTP系统文档（OTP系统的文档-XYZpdf，与XYZ为版本号），或者看看书的 Erlang和OTP在行动，因为在这本书有一服务不同零件从第一步骤，例如，使用二郎山/ 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".

恕我直言，这是目前各地的最好的书，因为它不仅介绍了二郎神，但也显示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.

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