rebar/test/upgrade_project/apps/dummy/src/dummy_sup.erl

-module(dummy_sup).
-behaviour(supervisor).

-export([start_link/0]).
-export([init/1]).

start_link() ->
    supervisor:start_link({local, ?MODULE}, ?MODULE, []).

init([]) ->
    Dummy = {dummy_server,
             {dummy_server, start_link, []},
             permanent, 5000, worker, [dummy_server]},

    {ok, {{one_for_one, 10, 10}, [Dummy]}}.
Add 'generate-upgrade' command 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. 2011-01-27 17:15:25 +00:00			`-module(dummy_sup).`
			`-behaviour(supervisor).`

			`-export([start_link/0]).`
			`-export([init/1]).`

			`start_link() ->`
			`supervisor:start_link({local, ?MODULE}, ?MODULE, []).`

			`init([]) ->`
			`Dummy = {dummy_server,`
			`{dummy_server, start_link, []},`
			`permanent, 5000, worker, [dummy_server]},`

			`{ok, {{one_for_one, 10, 10}, [Dummy]}}.`