| Age | Commit message (Collapse) | Author |
|---|
|
Do not try and ensure them for every app, there
are some OTP apps that only require kernel and
there's really no point in rewriting those.
|
|
lrascao/feature/empty_application_apps_silently_skipped
Ensure stdlib,kernel as application dependencies
|
|
Make this dependency explicit as it was causing
apps with empty application lists to not be included
in the generated release.
|
|
Fix OSX readlink
|
|
Only use multi-node sys.config if requested when replacing OS vars
|
|
Don't drop debug info on default build
|
|
It does not support the -f option.
|
|
When replacing OS vars only create multi-node sys.config
files (ie. filenames containing the node name) only if explicitly
requested. This is necessary because inclusion of other config
files inside of sys.config is only allowed if the file is actually called
sys.config and nothing else.
|
|
Drop it only when generating relx escript.
|
|
Drop use of export_all erlc directive
|
|
Starting from OTP20 this will trigger a warning, since we
use the warnings_as_errors the build would fail when using
this OTP release onwards.
|
|
Feature/fix crash on relup warning
|
|
Don't rewrite app files if contents are the same
|
|
Make use of warnings_on_errors option to exit
with error or proceed with just a warning.
|
|
When comparing .app files to check if a rewrite is
necessary do so by comparing erlang terms instead
of bytes, the original .app might contain comments
for example and cause unnecessary rewrites.
This proves a problem when dealing with erts .app
files that might be read-only at the origin and
thus cause a failed release on relx that is
uncalled for since there might have been no changes
at all.
|
|
Obtained from command line and saved in the state
to be used on situations where we want to error out on
warnings explicitly.
|
|
upgrade erlware_commons to 1.0.0 for OTP20 support
|
|
|
|
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
|
