<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rebar3.git/test/upgrade_project/apps/dummy/ebin, branch master</title>
<subtitle>Clone of https://github.com/erlang/rebar3</subtitle>
<link rel='alternate' type='text/html' href='https://git.sunet.se/rebar3.git/'/>
<entry>
<title>Add 'generate-appups' command</title>
<updated>2011-02-15T17:33:18+00:00</updated>
<author>
<name>joewilliams</name>
<email>joe@joetify.com</email>
</author>
<published>2011-02-10T21:27:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sunet.se/rebar3.git/commit/?id=11bf6b4aab33c273f0db94bded8763af68cbc167'/>
<id>11bf6b4aab33c273f0db94bded8763af68cbc167</id>
<content type='text'>
To further support OTP releases I have added support for generating
application appup files. These include instructions that systools uses
to generate a relup file which contains the low level instructions
needed to perform a hot code upgrade. My goal with this module is to
produce "good enough" appup files or at least a skeleton to help one get
started with something more complex. If an appup file already exists for
an application this command will not attempt to create a new one.

Usage:
$ rebar generate-appups previous_release=/path/to/old/version

Generally this command will be run just before 'generate-upgrade'.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
To further support OTP releases I have added support for generating
application appup files. These include instructions that systools uses
to generate a relup file which contains the low level instructions
needed to perform a hot code upgrade. My goal with this module is to
produce "good enough" appup files or at least a skeleton to help one get
started with something more complex. If an appup file already exists for
an application this command will not attempt to create a new one.

Usage:
$ rebar generate-appups previous_release=/path/to/old/version

Generally this command will be run just before 'generate-upgrade'.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add 'generate-upgrade' command</title>
<updated>2011-01-27T17:37:39+00:00</updated>
<author>
<name>joewilliams</name>
<email>joe@joetify.com</email>
</author>
<published>2011-01-27T17:15:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.sunet.se/rebar3.git/commit/?id=5298e93a180e6db87a33f26eb6a2db06e8065dc7'/>
<id>5298e93a180e6db87a33f26eb6a2db06e8065dc7</id>
<content type='text'>
To support OTP release upgrades I have added support for building
upgrade packages. Support for this is included in the
rebar_upgrade module, specifically generate_upgrade/2. It requires
one variable to be set on the command line 'previous_release' which
is the absolute path or relative path from 'rel/' to the previous
release one is upgrading from. Running an upgrade will create the
needed files, including a relup and result in a tarball containing
the upgrade being written to 'rel/'. When done it cleans up the
temporary files systools created.

Usage:
$ rebar generate-upgrade previous_release=/path/to/old/version

This also includes a dummy application that can be used to test
upgrades as well as an example.

Special thanks to Daniel Reverri, Jesper Louis Andersen and
Richard Jones for comments and patches.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
To support OTP release upgrades I have added support for building
upgrade packages. Support for this is included in the
rebar_upgrade module, specifically generate_upgrade/2. It requires
one variable to be set on the command line 'previous_release' which
is the absolute path or relative path from 'rel/' to the previous
release one is upgrading from. Running an upgrade will create the
needed files, including a relup and result in a tarball containing
the upgrade being written to 'rel/'. When done it cleans up the
temporary files systools created.

Usage:
$ rebar generate-upgrade previous_release=/path/to/old/version

This also includes a dummy application that can be used to test
upgrades as well as an example.

Special thanks to Daniel Reverri, Jesper Louis Andersen and
Richard Jones for comments and patches.
</pre>
</div>
</content>
</entry>
</feed>
