|serkus01 0418638463||2 weeks ago|
|bin||2 weeks ago|
|docker||2 weeks ago|
|erts-11.1.5||2 weeks ago|
|etc||2 weeks ago|
|lib||2 weeks ago|
|log/sasl||2 weeks ago|
|misc||2 weeks ago|
|releases||2 weeks ago|
|site||2 weeks ago|
|BuildInfo.txt||2 weeks ago|
|Makefile||2 weeks ago|
|README.md||2 weeks ago|
|do-plugins.escript||2 weeks ago|
|plugins.config||2 weeks ago|
|rebar||2 weeks ago|
|rebar.config||2 weeks ago|
|report.log||2 weeks ago|
|simple_bridge:8000.access||2 weeks ago|
|simple_bridge:8000.auth||2 weeks ago|
|yaws_dynopts.beam||2 weeks ago|
This is an Erlang web application using the Nitrogen Web Framework.
You can rebuild the project by typing:
If this fails, it likely means that its a slim release and Erlang is not installed on this machine. Please install Erlang.
You can start the application with:
which will start it in daemon mode. You can attach to this started daemon with:
If you’d rather have an Erlang console right away, rather than starting a daemon, type:
The rebar.config file controls dependencies and build parameters using the popular rebar tool.
plugins.config file controls how Nitrogen plugins are handled.
The files in the
etc directory control application configuration, including
ports, webserver set up, and the like. Please see the files there for
configuration options, or view the Nitrogen documentation.
Dependency libraries (once being built) end up in the
Source code can be found in
Template code is in
Compiled Erlang modules (ebin files) go in
By default Nitrogen comes with an application called sync which provides automatic code reloading when the related .erl file or .ebin file is updated. To use this, run the following on the Erlang shell: