| Age | Commit message (Collapse) | Author |
|---|
|
|
|
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.
|
|
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.
|
|
|
|
|
|
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.
|
|
When performing a relup that involves starting a new
application we need to inform release handler that the
code paths need to be updated to account for the new apps.
Otherwise the relup instruction application:start/2 will fail
since it is unable to find the .app file.
|
|
As described in http://erlang.org/doc/man/appup.html, when performing a relup
with soft purge:
If the value is soft_purge, release_handler:install_release/1
returns {error,{old_processes,Mod}}
|
|
bug description:
if vm.arg use '-sname xxx' option, When exec upgrade/install/unpack command, it will report "Hostname yyy is illegal" error.
|
|
|
