blob: 681b3eb3e3c08f2c70ba1164e92f3e41731894ed [file] [log] [blame]
David Reissae756f42008-06-10 22:57:11 +00001%%% -*- mode:erlang -*-
2{application, %APP_NAME%,
3 [
4 % A quick description of the application.
5 {description, "Thrift bindings"},
6
7 % The version of the applicaton
8 {vsn, "%VSN%"},
9
10 % All modules used by the application.
11 {modules, [
12 %MODULES%
13 ]},
14
15 % All of the registered names the application uses. This can be ignored.
16 {registered, []},
17
18 % Applications that are to be started prior to this one. This can be ignored
19 % leave it alone unless you understand it well and let the .rel files in
20 % your release handle this.
21 {applications,
22 [
23 kernel,
24 stdlib
25 ]},
26
27 % OTP application loader will load, but not start, included apps. Again
28 % this can be ignored as well. To load but not start an application it
29 % is easier to include it in the .rel file followed by the atom 'none'
30 {included_applications, []},
31
32 % configuration parameters similar to those in the config file specified
33 % on the command line. can be fetched with gas:get_env
34 {env, [
David Reiss920959a2008-06-11 00:56:35 +000035 % If an error/crash occurs during processing of a function,
36 % should the TApplicationException serialized back to the client
37 % include the erlang backtrace?
38 {exceptions_include_traces, true}
David Reissae756f42008-06-10 22:57:11 +000039 ]},
40
41 % The Module and Args used to start this application.
42 {mod, {thrift_app, []}}
43 ]
44}.