forked from vernemq/rebar3_cuttlefish
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ec424d8
commit e67890d
Showing
8 changed files
with
614 additions
and
107 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,26 +1,17 @@ | ||
rebar3_cuttlefish | ||
===== | ||
|
||
A rebar plugin | ||
This plugin provides cuttlefish and automatically updates the release configuration at runtime to utilize cuttlefish. | ||
|
||
Build | ||
----- | ||
Add the plugin to your top level rebar config: | ||
|
||
$ rebar3 compile | ||
{plugins, [rebar3_cuttlefish]}. | ||
|
||
Use | ||
--- | ||
|
||
Add the plugin to your rebar config: | ||
The cuttlefish release and tar providers need | ||
|
||
{plugins, [ | ||
{rebar3_cuttlefish, {git, "git@github.com:tsloughter/rebar3_cuttlefish.git", {branch, "master"}}} | ||
]}. | ||
$ rebar3 cuttlefish release | ||
|
||
Then just call your plugin directly in an existing application: | ||
The plugin provider will tell relx to create the dirs `share/schema` in the release, copy the cuttlefish escript to `bin/` and discover all schema files in the project apps and their dependencies. | ||
|
||
|
||
$ rebar3 cuttlefish | ||
===> Fetching rebar3_cuttlefish | ||
===> Compiling rebar3_cuttlefish | ||
===> Running cuttlefish schema generator | ||
Since cuttlefish uses sort order of the schema files by their name you may want to prepend a number to the schema file name, like `01-eleveldb.schema`. While the plugin will automatically copy all schema files for you it will first check if there is already an overlay entry for each schema file. So if in `overlay` there is an entry `{template, "schema/eleveldb.schema", "01-eleveldb.schema"}` it will not make another copy. |
Oops, something went wrong.