rebar3_appup_plugin
rebar3_appup_plugin copied to clipboard
lrascao
A rebar3 plugin for frictionless release upgrades
My problem is the following: As far as I know `rebar3 appup generate` currently generates {upgrade, Mod, ...} instructions into the .appup file only if the module has been changed...
I add a new child under a supervisor process, the new module is added, but the child process does not start. The spec in the supervisor is: ``` erlang init([])...
### Environment ### -bash-4.2$ rebar3 report ``` Rebar3 report version 3.5.3+build.4088.refe2e7f65 generated at 2018-06-20T14:40:40+00:00 ================= Please submit this along with your issue at https://github.com/erlang/rebar3/issues (and feel free to edit out...
I'm generating appup file for my svn hosted project. I have two branches names **rel_v0_1_0** and **rel_v0_2_0**. Both are identical except application version I have changed. Here is output of...
Hi This is not a bug, but a possible feature request. We have around 60 erlang repos. All of them use appup plugin by either generating appup from appup.src calling...
when calling appup release, which calls appup compile on one of our applications it generates {"git", UpgradeInstructions, DowngradeInstructions} instead of putting the correct version number there. The version number comes...
When I add `encrypt_debug_info` to `erl_opts`,I found some modules that I did not make changes in the appup file.Then I found this from otp's [source](https://github.com/erlang/otp/blob/a98379d0519c28f9bc9b673ed2c09fb1ad52456e/lib/compiler/src/compile.erl#L1437), It use `crypto:strong_rand_bytes/1` when encrypt...
