<div dir="ltr">Cool! Thanks Fred!</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 5, 2014 at 4:54 PM, Fred Hebert <span dir="ltr"><<a href="mailto:mononcqc@ferd.ca" target="_blank">mononcqc@ferd.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The buildpack at <a href="https://github.com/archaelus/heroku-buildpack-erlang" target="_blank">https://github.com/archaelus/heroku-buildpack-erlang</a><br>
works with every release from R15B to R17B pre. The old one under<br>
Heroku's own github account is deprecated and points to the one above.<br>
<br>
Which OTP release to be used will be picked based on the<br>
.preferred_otp_version file in your repository.<br>
<br>
Regards,<br>
Fred.<br>
<div><div class="h5"><br>
On 02/05, Mark Nijhof wrote:<br>
> That build pack seems out of date, I looked at this for a little while back<br>
> for a personal little thing but I think it was for r15. Is there an updated<br>
> fork, or does it just work?<br>
><br>
> -Mark<br>
><br>
><br>
> On Wed, Feb 5, 2014 at 2:57 PM, Sean Cribbs <<a href="mailto:sean@basho.com">sean@basho.com</a>> wrote:<br>
><br>
> > I'm sure Tristan and Geoff will tell you, there is a buildpack that makes<br>
> > it pretty easy to deploy Erlang applications on Heroku. It doesn't build<br>
> > releases, but it does builds and deploys your project directly from a "git<br>
> > push", which is pretty awesome.<br>
> ><br>
> > <a href="https://github.com/archaelus/heroku-buildpack-erlang" target="_blank">https://github.com/archaelus/heroku-buildpack-erlang</a><br>
> ><br>
> ><br>
> > On Wed, Feb 5, 2014 at 2:55 PM, Dmitry Kolesnikov <<a href="mailto:dmkolesnikov@gmail.com">dmkolesnikov@gmail.com</a>>wrote:<br>
> ><br>
> >> Hello,<br>
> >><br>
> >> The release is extremely great feature, from my perspective.<br>
> >> You can product "self" deployable packages with help of bash magic.<br>
> >> This makes not needs to have Erlang pre-installend on any of the target<br>
> >> machines.<br>
> >><br>
> >> - Dmitry<br>
> >><br>
> >> On 05 Feb 2014, at 15:49, Ivan Uemlianin <<a href="mailto:ivan@llaisdy.com">ivan@llaisdy.com</a>> wrote:<br>
> >><br>
> >> Isn't (part of) the point of erlang releases that you don't need erlang<br>
> >> pre-installed?<br>
> >><br>
> >> Ivan<br>
> >><br>
> >> --<br>
> >> festina lente<br>
> >><br>
> >><br>
> >> On 5 Feb 2014, at 12:44, Vance Shipley <<a href="mailto:vances@motivity.ca">vances@motivity.ca</a>> wrote:<br>
> >><br>
> >><br>
</div></div><div class="im">> >> On Feb 5, 2014 5:01 PM, "Loïc Hoguin" <<a href="mailto:essen@ninenines.eu">essen@ninenines.eu</a>> wrote:<br>
> >> ><br>
> >> > Pardon my ignorance but what does a Java hosting company do exactly<br>
> >> compared to just getting a server?<br>
> >><br>
> >> When I hear "Java hosting" or "Erlang hosting" I think of cloud<br>
> >> environments which provide JVM or BEAM virtual machines (emulators) where<br>
> >> you aren't bothered by operating systems. You pay for instances of the VMs<br>
> >> and transactional bandwidth. This is what Google AppEngine provides for<br>
> >> Java, Python and Go. I've developed cloud services using Go on Appengine<br>
> >> and it was wonderfully clean and simple.<br>
> >><br>
</div>> >> One future for Erlang may be the LING VM from <a href="http://erlangonxen.comwhich" target="_blank">http://erlangonxen.comwhich</a> runs directly on the Xen hypervisor which is wicked cool. I've got<br>
<div><div class="h5">> >> big hope for this.<br>
> >><br>
> >> But in practice I'm sure that it means Linux VMs with Erlang/OTP<br>
> >> preinstalled.<br>
> >><br>
> >> _______________________________________________<br>
> >> erlang-questions mailing list<br>
> >> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> >> <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> >><br>
> >> _______________________________________________<br>
> >> erlang-questions mailing list<br>
> >> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> >> <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> >><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> erlang-questions mailing list<br>
> >> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> >> <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> >><br>
> >><br>
> ><br>
> ><br>
> > --<br>
> > Sean Cribbs <<a href="mailto:sean@basho.com">sean@basho.com</a>><br>
> > Software Engineer<br>
> > Basho Technologies, Inc.<br>
> > <a href="http://basho.com/" target="_blank">http://basho.com/</a><br>
> ><br>
> > _______________________________________________<br>
> > erlang-questions mailing list<br>
> > <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> > <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
> ><br>
> ><br>
><br>
><br>
> --<br>
> Mark Nijhof<br>
</div></div>> t: @MarkNijhof <<a href="https://twitter.com/MarkNijhof" target="_blank">https://twitter.com/MarkNijhof</a>><br>
> s: marknijhof<br>
<div class="HOEnZb"><div class="h5"><br>
> _______________________________________________<br>
> erlang-questions mailing list<br>
> <a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
> <a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Mark Nijhof<br><div><div>t: <a href="https://twitter.com/MarkNijhof" target="_blank">@MarkNijhof</a><br>s: marknijhof</div></div>
<div><br></div></div>
</div>