From d2a3f2cedd7c00d0933222aed9c06b3149aa4db4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Wed, 4 Apr 2018 13:13:37 +0200 Subject: Cowboy 2.3.0 --- docs/en/erlang.mk/1/guide/releases/index.html | 34 +++++++++++++-------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'docs/en/erlang.mk/1/guide/releases') diff --git a/docs/en/erlang.mk/1/guide/releases/index.html b/docs/en/erlang.mk/1/guide/releases/index.html index 0ee51c52..494c27c3 100644 --- a/docs/en/erlang.mk/1/guide/releases/index.html +++ b/docs/en/erlang.mk/1/guide/releases/index.html @@ -7,7 +7,7 @@ - + Nine Nines: Releases @@ -78,7 +78,7 @@ file in the $(RELX_CONFIG) location. This defaults to $(CURDIR)/relx.config. You can override it by defining the variable before including Erlang.mk:

-
@@ -95,7 +95,7 @@ location defaults to $(CURDIR)/relx and can be overriden.

You can specify additional Relx options using the RELX_OPTS variable. For example, to enable dev_mode:

-
@@ -105,7 +105,7 @@ in the Relx options directly, Erlang.mk provides a specific variable for it: RELX_OUTPUT_DIR. It defaults to the _rel directory. You can also override it:

-
@@ -120,7 +120,7 @@ release. As mentioned before, Erlang.mk will automatically generate it when it detects the $(RELX_CONFIG) file. This means the following command will also build the release:

-
@@ -128,7 +128,7 @@ http://www.gnu.org/software/src-highlite -->

If you need to generate the release, and only the release, the rel target can be used:

-
@@ -144,7 +144,7 @@ located at $(RELX_OUTPUT_DIR)/<name>/<name>-<vsn>.tar.gz

Erlang.mk provides a convenience function for running the release with one simple command:

-
@@ -174,7 +174,7 @@ release will be example.

Once all this is done, you can build the tarball for the release upgrade:

-
@@ -184,7 +184,7 @@ release, $RELX_OUTPUT_DIR/example/example-2.tar.gz.

Move the archive to the correct location on the running node. From the release’s root directory:

-
@@ -192,14 +192,14 @@ http://www.gnu.org/software/src-highlite --> $ mv path/to/example-2.tar.gz releases/2/

Finally, upgrade the release:

-
$ bin/example_release upgrade "2/example_release"

Or on Windows:

-
@@ -214,14 +214,14 @@ http://www.gnu.org/software/src-highlite --> generated by Relx based on VCS history.

Create a file rel/version with only one line inside:

-
{{ release_version }}

Add/Update the overlay section of your relx.config:

-
@@ -231,7 +231,7 @@ http://www.gnu.org/software/src-highlite -->

When you run make rel it creates the file $(RELX_OUTPUT_DIR)/example/version which contains the version value generated by Relx.

-
@@ -240,14 +240,14 @@ http://www.gnu.org/software/src-highlite -->

In your Makefile you can use this simple snippet to get the version, but please keep in mind that this should depend on the rel target:

-
$(shell cat $(RELX_OUTPUT_DIR)/$(RELX_REL_NAME)/version)

For example:

-
@@ -258,7 +258,7 @@ http://www.gnu.org/software/src-highlite --> echo APP_VERSION = $(APP_VERSION)

Would output:

-
-- cgit v1.2.3