Moving a slim release to a system with a different version of Erlang #59

choptastic opened this Issue Sep 23, 2013 · 1 comment


None yet
1 participant

choptastic commented Sep 23, 2013

Currently, if you move a generated slim release to a machine with a different version of Erlang, it will simply fail to start. The "easy" solution is to generate a release on the target machine and replace the contents of the "releases" directory.

This is a hack approach, however, there should be a more elegant solution. Ideally something like make fix-release or something.


choptastic commented Apr 22, 2014

Solved with make fix-slim-release using this commit: ae78f83

It's a kludgy, nasty thing, but it does the job for now.

@choptastic choptastic closed this Apr 22, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment