charpi / erl_rake
- Source
- Commits
- Network (6)
- Issues (0)
- Downloads (1)
- Wiki (1)
- Graphs
-
Tree:
b744f42
charpi (author)
Thu Oct 22 12:01:28 -0700 2009
commit b744f426d38fabc549bd9982f86b690746764766
tree 9a141748c50c91733e6ad3611f7b3fff05e8c6d3
parent 2660849171989eb4a41b6c4f64bddafecd1958ba
tree 9a141748c50c91733e6ad3611f7b3fff05e8c6d3
parent 2660849171989eb4a41b6c4f64bddafecd1958ba
erl_rake /
| name | age | message | |
|---|---|---|---|
| |
AUTHORS | Sat Jan 24 09:19:34 -0800 2009 | |
| |
README | ||
| |
Rakefile | Thu Oct 22 12:01:28 -0700 2009 | |
| |
lib/ | Thu Oct 22 12:01:28 -0700 2009 | |
| |
rakelib/ |
README
Sample erlang application to demonstrate the use of rake tasks dedicated to erlang.
= Installation =
Put in your project the directory 'rakelib' it contains all '.rake'
files and some escript needed by tasks.
= Usage =
rake --tasks : to know all tasks
You'll need a configuration in which you'll have to put things specific to your installation.
A template of file is generated the first time you launch 'rake'
Here is some useful tasks:
rake erlang:modules: Compile all erlang source files (test included)
rake erlang:releases: Build a tarball for each rel file found in the directory tree
rake erlang:tests[name]: Run the eunit test for the application "name". If no name is given,
all applications are tested. If a file test.desc is find in the "app_name/test" directory, eunit will
use it as eunit test description.
rake erlang:edoc[name]: Build the document for an application or all if 'name' is omitted
rake otp:new_application[name]: Create a new application squeleton
rake otp:start_local[name]: Start a release in the developper environment
rake otp:initial_target[name,version]: Create a tarball with a 'ready' to deploy
an erlang system running the release. To use the system, you have to provide
2 startup files in a directory named 'release_config'. Look at the sample in the
application sample_rake.
= Author =
Nicolas Charpentier <open_source@charpi.net>

