| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Add test coverage for long node name releases
|
|
|
|
Obtain release node name from Erlang VM instead of OS
|
|
|
|
Replace rebar_log in assembler
|
|
builders other then rebar(Erlang.mk)
|
|
upgrade erlware_commons
|
|
|
|
Bump cf to 0.2.2
|
|
|
|
Fix duplicated method
|
|
Introduced while merging PRs 445, 541
|
|
Provide a new config directive that allows per-app module exclusion
|
|
Add script to help in generating release changelog
|
|
Allow upgrade/downgrade from non-permanent versions
|
|
Add support for new relx directive that provides start/stop script hooks
|
|
By introducing a new entry in the config file allow excluding
specific modules from a given app, they will not be copied
onto the final release and their reference removed from
the .app file. The new entry takes on the following form:
{exclude_modules, [
{App :: atom(), [Module :: atom()]}
]}
|
|
|
|
New 'extended_start_script_hooks' directive that allows the
developer to define six different hook shell scripts to be invoked
at pre/post start/stop/install upgrade phases.
Besides these custom defined scripts, other types of builtin
scripts are also available, these offer pre-packaged functionality
that can be used directly, they are:
pid - writes the beam pid to a configurable file location
(/var/run/<rel_name>.pid by default).
wait_for_vm_start - waits for the vm to start (ie. when it responds to pings)
wait_for_process - waits for a configurable name
to appear in the erlang process registry
The hook scripts are invoked with the 'source' command, therefore
they have access to all the variables in the start script.
|
|
Now that you can upgrade to a new version
without setting it as permanent you should also
be able to downgrade from it, this allows downgrading
or upgrading to a version that is already marked as
permanent but is not actually currently running.
|
|
Move it next to console since it's mostly the
same thing but with extra parameters.
|
|
Remove name collisions of replaced files in multi-node setups
|
|
|
|
Feature/optional permafy relup
|
|
Support a command line argument to the `upgrade`/`downgrade`
commands: `--no-permanent`, if this is set the release will be unpacked,
installed and be made current but not permanent, when the user
is confortable with the outcomehe can issue the same command a
second time without the `--no-permanent` option.
|
|
|
|
Support the uninstall command. (release_handler:remove_release/1)
|
|
|
|
|
|
Fix head mismatch
|
|
|
|
lrascao/feature/flexible_release_package_location_on_relups
Feature/flexible release package location on relups
|
|
Instead of forcing the user to put the tarball package
with the expected name (<relname>.tar.gz)and in the
expected location (releases/<version>) symlink this
fixed file name to a tarball existing in one of three different
places (releases/, releases/<version>,
releases/<version>/<relname>.tar.gz).
Refactor the install/upgrade escript to make it more
dynamic, it now runs commands that are passed from
the start script while accepting a variable number
of arguments.
Add a `versions` command to the extended start
script that prints out the currently installed versions
and their status.
|
|
The second argument is actually the version and
not the package name.
|
|
Patch to fix #523
|
|
Issue 1: If RELX_REPLACE_OS_VARS is true then existing vm.args (sys.config) file
is renamed to vm.arg.orig (sys.config.orig) and a new vm.args (sys.config) is
generated. However, if for some reason new vm.args (sys.config) is not generated
then system ends up without a valid vm.args (sys.config) file and keeps failing
thereafter.
Issue 2: Continuing from issue 1, if the system does not have sufficient
disk space or the current directory is immutable then new vm.args (sys.config)
will not be generated.
This patch tries to fix both the above issues by keeping the existing
vm.args (sys.config) untouched and creates a new vm.args (sys.config)
in /tmp directory
|
|
Feature/nicer templates ng
|
|
+Bi disables the erlang break functionality
|
|
useful if deploying erlang nodes via capistrano
when TERM is not set correctly attaching to the
node will result in weirdness
|
|
(see: http://erlang.org/pipermail/erlang-patches/2010-March/000883.html)
|
|
Give code path access to console_clean
|
|
To allow manually loading and starting up
applications.
|
|
Feature/replace os vars test
|
|
The first run would correctly replace the environment
variables, however it would also overwrite the original
vm.args and sys.config thus preventing any further
substitution in subsequent runs.
Dev mode runs were also broken, all runs after the
first were required to also define the
RELX_REPLACE_OS_VARS variable in order not to
overwrite the current vm.args with the original one,
this prevented simply attaching to an already running
node that was started this way.
Add tests to exercise this functionality.
|
|
Revert "remove rlx_topo since all systools >=R15 have a working sort of apps"
|
|
This reverts commit 701da7b9f2dfb872351b56938f7aed5bff0d79c7.
|
|
lrascao/feature/include_nodetool_on_extended_start_script
Always include nodetool when generating extended start script
|
|
Remove redundant check for extended_start_script.
Add tests that enforce this invariant.
|
|
Fixed: #524. Erts src folder existence check added
|
