<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">The only problem you can run into is
application dependencies not being started automatically, and
issues related to that (i.e., related to not having a real release
to use for application startup). There is some code that can help
you here <a class="moz-txt-link-freetext" href="https://github.com/okeuday/reltool_util">https://github.com/okeuday/reltool_util</a>, if you need it.<br>
<br>
On 06/01/2013 07:26 PM, Jeremy Ong wrote:<br>
</div>
<blockquote
cite="mid:CAKD1GY5PAxxjJ3PowgsCpqoXHxMUqvQVJcArY50GqjkQXyWD4Q@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_default">I believe you said it yourself. Don't
use reltool in your development cycle. Reltool is for
generating releases and going through the whole rigamarole for
small iterations is overkill. Write a simple shell script to
launch erl with all your code paths and start rustyio/sync for
development. Before you release or perform a code upgrade,
loop in rebar generate at that point.<span> </span></div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sat, Jun 1, 2013 at 7:15 PM, Felix
Gallo <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:felixgallo@gmail.com" target="_blank">felixgallo@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote">
<div dir="ltr">I'm developing a medium-sized erlang node
comprised of several interacting applications. In doing
so, I'm finding myself staring at the output of
<div>
<br>
</div>
<div>./rebar compile && ./rebar generate
&& ./rel/bin/mynode/bin/mynode console</div>
<div><br>
</div>
<div>quite a bit more than is perhaps wanted.</div>
<div><br>
</div>
<div>I thought that <a moz-do-not-send="true"
href="https://github.com/rustyio/sync" target="_blank">https://github.com/rustyio/sync</a>
might be the answer to all of my problems, as it
advertises hot code reloading on file changes. However,
I haven't yet coaxed it into working inside the
./rel/bin/mynode/bin/mynode console environment; I
suspect it's detecting the code changes, and recompiling
the code, but it's not redeploying into the release, so
doesn't reload the beams.</div>
<div><br>
</div>
<div>So then I thought that maybe it's dumb to include the
reltool build in the development cycle, maybe the pro
erlang way is to just run erl by hand like our
forefathers did before us. But when I give that a shot,
as an OTP neophyte, I have this lurking feeling that I
am aiming a gun at my foot.</div>
<div><br>
</div>
<div>For those of us who don't believe in emacs, what's
the one true optimal way to tighten up the development
loop here?</div>
<span class="HOEnZb">
<div><br>
</div>
<div>F.</div>
</span></div>
<br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a moz-do-not-send="true"
href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a moz-do-not-send="true"
href="http://erlang.org/mailman/listinfo/erlang-questions"
target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-questions mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-questions">http://erlang.org/mailman/listinfo/erlang-questions</a>
</pre>
</blockquote>
<br>
</body>
</html>