-
Notifications
You must be signed in to change notification settings - Fork 296
Conversation
Have hot upgrade been tested against a slim release? |
Not yet. I will try soon. |
Oops, upgrade does not work against a slim release :-/ ,
|
@shino, ping? |
Hey guys, Has any progress been made in the slim releases? |
Rebased on master to avoid merge conflict. Error in upgrade is caused by release_handler. It seems to be not yet slim release compatible.
So this slim release support does not work with upgrade at present. P.S. Trace of release_handler calls by redbug (for curious people):
|
Siri told me the workaround
So now (very simple) upgrading can be done in slim release. |
Workaround to upgrade is found and it may be implemented by upgrade script. I hope it is now ready for review again :) |
@jaredmorrow ping? |
This looks fine to us. Can you rebase this so it merges cleanly and then I'll merge. |
Rebased on current master fa1a2b5 . |
ping! can this be merged? (It would be good to add some lines in the wiki as well @shino ) |
PR for #7 .
By adding
{excl_lib, otp_root}
to reltool.config,generate a slim release which does not include erts and otp libraries.
Also the runner script uses appropriate options for slim release.
Example:
erts_vsn
directory is not created in slim release as it should be.Therefore
nodetool
script is moved to underreleases/$APP_VSN/
(as template)and
erl
script should be removed from overlay (by editing).rebar generate
creates a marker file$RUNNER_BASE_DIR/releases/$APP_VSN/runner_script.data
.runner scripts know whether slim release or not(=normal) by its content.
just because my Erlang/OTP is built without hipe.