rebar/test/upgrade_project/apps/dummy/src/dummy_server.erl
joewilliams 5298e93a18 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 18:37:39 +01:00

56 lines
1.1 KiB
Erlang

-module(dummy_server).
-behaviour(gen_server).
-export([start_link/0, set_state/1, get_state/0]).
-export([init/1,
handle_call/3,
handle_cast/2,
handle_info/2,
terminate/2,
code_change/3]).
%%
start_link() ->
gen_server:start_link({local, ?MODULE}, ?MODULE, [], []).
set_state(What) ->
gen_server:call(?MODULE, {set_state, What}).
get_state() ->
gen_server:call(?MODULE, get_state).
%%
init([]) ->
say("init, setting state to 0", []),
{ok, 0}.
handle_call({set_state, NewState}, _From, _State) ->
{reply, {ok, NewState}, NewState};
handle_call(get_state, _From, State) ->
{reply, State, State}.
handle_cast('__not_implemented', State) ->
{noreply, State}.
handle_info(_Info, State) ->
say("info ~p, ~p.", [_Info, State]),
{noreply, State}.
terminate(_Reason, _State) ->
say("terminate ~p, ~p", [_Reason, _State]),
ok.
code_change(_OldVsn, State, _Extra) ->
say("code_change ~p, ~p, ~p", [_OldVsn, State, _Extra]),
{ok, State}.
%% Internal
say(Format, Data) ->
io:format("~p:~p: ~s~n", [?MODULE, self(), io_lib:format(Format, Data)]).