| Age | Commit message (Collapse) | Author |
|---|
|
|
|
PIPE_DIR handling
|
|
As mentioned in the (closed) issue #127, the default pipe directory is not multi-user friendly. When running multiple relx-generated releases as different users, the first to be started will create the /tmp/erl_pipes directory, which the ones starting after that cannot create their pipe dirs in. The ticket mentions that this should be fixed by #154, but I cannot see how this is supposed to solve the issue. Right now, the only way I see is to use prefix the start command with env PIPE_DIR=/some/other/dir/, which is quite cumbersome.
This change will work exactly as before when PIPE_DIR is explicitly set. In case PIPE_DIR is not set, however, it will first attempt to create the parent dir /tmp/erl_pipes with mode 1777, which should enable releases being run as other users to create their pipe dirs.
|
|
|
|
|
|
Prevent .erlang from prepending string to the erl root dir
|
|
Any output string from .erlang to stdout will be prepend to
code:root_dir(), so it will cause the retrieved dir incorrect.
The fix is to start erl with the no_dot_erlang boot file.
|
|
|
|
|
|
Don't fail status script command if empty
|
|
Let people define their own when they want to.
|
|
|
|
Add OTP20 support
|
|
|
|
Fixing windows paths for bin scripts
|
|
The syntax for proper path handling when the path may contain
parentheses (such as C:\Program Files (x86)\...) requires quoting the
entire assignment expression:
set "var=%val%"
any other way of doing it may interpret the parentheses and cause
failures.
|
|
Rename gb_tree:tree to gb_trees:tree
|
|
|
|
Windows bat file has an error, causing upgrade to not work
|
|
be 'install' or 'unpack'
|
|
Update README.md
|
|
|
|
Have Travis run on latest OTP19.3
|
|
Feature/extended start script status
|
|
Provide a status command to start script which,
by default, runs a builtin hook that simply prints
which applications are running in the node.
This hook can then be customized to print whatever
the user wants by adding
{status, [{custom, "path/to/hook"}]}
to already existing extended_start_script_hooks.
|
|
|
|
|
|
add osx configuration to .travis.yml
|
|
|
|
Only ensure kernel,stdlib for empty dep apps
|
|
Don't require compiler in the release for relups
|
|
|
|
Add the ability to chmod files in the overlay.
|
|
Two types are supported, direct chmoding, like
{chmod, 8#00700, "path/to/file/maybe/with/{{templates}}" }
or templating the permission where you have a template var like
{file_perm, 8#00700}
and an overlay
{chmod, "{{file_perm}}","path/to/file/maybe/with/{{templates}}" }
|
|
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.
|
