You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When starting an LFE release with rebar3 lfe run-release start sometimes it doesn't actually start (checked by running rebar3 lfe run-release ping). However, almost always after running rebar3 release again, it will start, with a subsequent ping resulting in a pong.
Things to test:
Generate a new project with rebar3 new lfe-release
Generate a release for the project with rebar3 release
Run the release script manually (./_build/..../app-name start)
do several series of starts and stops, pinging each time
make sure it always comes up
Now run the rebar3 lfe run-release start command (without rebuilding the release) to check its behaviour
Do a fresh rebuild of the release, and check again
Create a new Erlang/OTP release (no LFE) using rebar3 new release
update the project's rebar.confg file and add the LFE plugin
use the LFE plugin command to run through the same steps above to see if the results are all the same
The text was updated successfully, but these errors were encountered:
When starting an LFE release with
rebar3 lfe run-release start
sometimes it doesn't actually start (checked by runningrebar3 lfe run-release ping
). However, almost always after runningrebar3 release
again, it will start, with a subsequentping
resulting in apong
.Things to test:
rebar3 new lfe-release
rebar3 release
./_build/..../app-name start
)rebar3 lfe run-release start
command (without rebuilding the release) to check its behaviourrebar3 new release
rebar.confg
file and add the LFE pluginThe text was updated successfully, but these errors were encountered: