Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Check out rebar: <b><a href="https://github.com/basho/rebar" rel="noreferrer"><a href="https://github.com/basho/rebar" rel="noreferrer">https://github.com/basho/rebar</a></a></b> used for packaging, templating and managing releases of Erlang/OTP applications. You will find there an entire tutorial on how to use it.<br><br>Check out <b><a href="http://learnyousomeerlang.com/what-is-otp#its-the-open-telecom-platform" rel="noreferrer">this tutorial on OTP</a></b> first, before you can <b><a href="http://learnyousomeerlang.com/release-is-the-word" rel="noreferrer">switch to this one</a></b> which shows you releases and how they are handled in Erlang. Use this <b><a href="http://learnyousomeerlang.com/contents" rel="noreferrer">entire book as reference</a></b> as you develop your project and because the author is still progressively adding more advanced stuff that you may need.<br><br> You may also want to keep reading about <b><a href="http://www.erlang.org/doc/design_principles/applications.html" rel="noreferrer">Erlang Applications</a></b> and then do check out these quick links below: <br><br> <b><a href="https://support.process-one.net/doc/display/CONTRIBS/Erlang+packaging" rel="noreferrer">Erlang Packaging, Process One</a><br><a href="http://chicagoerlangusergroup.blogspot.com/2010/02/otp-packaging-video-12162009.html" rel="noreferrer">OTP Packaging Video by Chicago Boss Guys</a><br><a href="http://www.studiomediatech.com/not-a-blog/2011-01-17/erlang-dependency-management" rel="noreferrer">Erlang Dependency Management</a><br><a href="http://www.metabrew.com/article/erlangotp-releases-rebar-release_handler-appup-etc" rel="noreferrer">Richard Jones Advice and examples on Packaging Erlang Projects with Dependencies</a><br><a href="http://www.trapexit.org/Maven_and_Erlang" rel="noreferrer">Maven Tool and how it is used in packaging Erlang Projects</a></b></p> <p>Most importantly, take <code>rebar</code> very seriously ! It is very important in managing Erlang applications which have dependencies. You can keep Posting your questions here on stackoverflow for any assistance as you progress.<br><br> Before i forget, do check out alot of stuff from the <b><a href="http://basho.com/community/" rel="noreferrer">Riak Community</a></b></p> <p><b>EDIT</b><br><br> Also, its important to check out the system documentation on <b><a href="http://www.erlang.org/doc/system_principles/create_target.html" rel="noreferrer">creating target systems</a></b> and also how to use <b><a href="http://www.erlang.org/doc/man/reltool.html" rel="noreferrer">Reltool</a></b> to handle releases. The good thing with erlang is that it has several options of how to do something, as long as its easy to maintain your application in that way. With target systems, you will learn how to embed the Erlang VM, how to run Erlang applications on <code>Solaris</code>, <code>VxWorks</code>,and creating Erlang applications as Services on Windows NT using <b><a href="http://www.erlang.org/doc/man/erlsrv.html" rel="noreferrer">erlsrv</a></b>.<br><br>Normally, we make sure that as an operating system is booting a Server, our application starts with it. Solaris is so far has more customizations than any other OS as regards embedding Erlang/OTP VM. You can always communicate with (an) embedded Erlang VM(s) using <b><a href="http://www.erlang.org/doc/man/escript.html" rel="noreferrer">Escript</a></b> where by the escript creates a an erlang node which is allowed to connect to the embedded VM (so they have to share same cookie) and the embedded VM must have allowed the temporarily created Node to connect by executing <pre>net_kernel:allow(List_of_nodes)</pre>, you make sure to call this method to make your embedded VM allow connections only from an known strictly specified number of Nodes.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload