| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
- The OTP app template now adds the supevisor
- The default apps_dir value does not contain the trailing '/' that the
template index already added.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The first variable can be unkeyed and the provider will sub in the
variable name 'name'. Additionally, the built-in templates and
documentation have been updated so that 'appid' is now 'name' and the
alternative commands are shown.
|
|
|
|
|
| |
This totally breaks compatibility with rebar2, and maybe it shouldn't
have.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
When a node is configured with -sname the REMSH_NAME_PART argument should be defined with using command 'hostname' but error occurs due extra space
|
| |
|
| |
|
| |
|
|\
| |
| | |
Incorrect REMSH args when sname is used.
|
| |
| |
| |
| |
| | |
To avoid problems with REMSH node being visible from another nodes
starts it in hidden mode (erl -hidden).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a node is configured with -sname in app.config or sys.config the
REMSH_NAME_ARG and REMSH_REMSH_ARG arguments are incorrect due the
assumption that the node name always contains '@'.
To fix the bug, the script tries to find '@' and then compose the
arguments acording to node name type. If in long name mode the
script can't compose a correct node name exits with warning.
|
| | |
|
| | |
|
|/
|
|
|
| |
RUNNER_SCRIPT variable is not initialized in simplenode.runner and it's
referenced when calling sudo.
|
|\
| |
| | |
Remove leading empty line from a template
|
| | |
|
|\ \
| | |
| | | |
Use "pwd -P" to get the current physical path.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It is a portable version of the realpath(1) utility that you can find on
Mac OS X and FreeBSD (see also The Open Group Base Specifications Issue
6, IEEE Std 1003.1).
Without the -P flag, pwd(1) might return different values when the
current path contains one or more symlinks, depending on how you got
into the current directory.
In simplenode.runner, this may cause PIPE_DIR to have different values
on each use, which will make it impossible to connect to the running
node unless you guess the correct path yourself.
|
|/ / |
|
| |
| |
| |
| | |
This removes the dependency on lib/compiler in an OTP release.
|
| |
| |
| |
| |
| |
| | |
As discussed here
http://erlang.org/pipermail/erlang-questions/2012-December/071135.html
change the reltool spec to use the default sys-level mod_cond setting.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
When developing Riak, we have found bugs and other issues due
to the number of platforms we support.
Here is an overview of the changes:
- Fix command-line syntax for commands to work on *BSD / Sun
- Add chkconfig and getpid to nodetool
- Replace platform specific 'kill' commands with a nodetool
getpid method
- Fix RUNNER_USER settings to work on *BSD
|
|
|
|
|
| |
This allows the node to run in paths which include special characters,
for example 'C:\Program Files (x86)\Product Name'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch contains two additions to simplenode.runner:
1. Check if vm.args exists in CWD; if so, use it. This makes it
easier to start multiple concurrent nodes on a single machine
from one rebar-created release (starting each node from its
own directory, with its own copy of vm.args and e.g.
sys.config, log directory, database directory, etc.)
2. Add the targets start_boot <file> and console_boot <file>.
This is used to select a different boot script. The 'setup'
application (http://github.com/esl/setup) builds a special boot
script for installation (all apps loaded but not started,
making it possible to run install hooks with the full code path
in place).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Typos and other minor bug fixes
* Add "attach" command (via -remsh)
* Add "upgrade" command to install a hot upgrade package
* Add "upgrade" subcommand to UNIX runner script as well
|
| |
|
| |
|
|
|
|
|
|
| |
bin/<release_name> console -kernel test '[{"a","b"}]' fails, because
when $@ is inserted into CMD [{"a","b"}] is interpreted.
Fix the same issue for 'start' command and quote all arguments.
|
| |
|