Heroku is a tremendous asset for ruby developers, but it is also very restrictive. Heroku has infrastructure components to satisfy 90% of web apps, but when you want to use something they don't support you need an alternative deployment solution. Also, some apps need better disk performance then amazon can provide.<div>
<br></div><div>So LambdaEngine would be awesome, but the haskell web community still needs a general purpose deployment tool. Unfortunately there isn't even a haskell SSH library available right now. <div><div>
<br></div><div>As you outlined: We can deploy a production binary to a free micro instance. To modify the idea of a compiler instance slightly, I would call it a staging server. it would not be brought up by the production instance, but instead by the user as part of the deployment process. That way the production instance can stay dumb, and the staging instance can also be used to test the application before deploying it to production. And of course, the staging sever can be shut down and spun up on demand to save cost.</div>
<div>Here is a ruby deployment tool with amazon integration to give an idea of what I am shooting for: <a href="https://github.com/wr0ngway/rubber/wiki/Quick-Start">https://github.com/wr0ngway/rubber/wiki/Quick-Start</a></div>
<div><br></div>
<div>In my mind, general deployment tools could provide a springboard for making LambdaEngine, although there would certainly be some amount of divergence.</div><div><br></div><div><div><div class="gmail_quote">On Sat, Mar 26, 2011 at 10:32 AM, Michael Snoyman <span dir="ltr"><<a href="mailto:michael@snoyman.com" target="_blank">michael@snoyman.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
JP Moresmau recently sent me an email asking for recommendations on<br>
hosting a Yesod app. I think a number of you have heard me mention the<br>
idea of setting up a WAI web hosting system (code named Lambda<br>
Engine). I think it's time to start hitting this idea hard, and I'd<br>
like community involvement as much as possible.<br>
<br>
I think we have two extremes we can approach this from: at the one<br>
end, we can provide a complete hosting solution, similar to Heroku[1].<br>
People would simply "cabal sdist" their project, type "lambda-engine<br>
upload mytarball.tar.gz" and their site would be live. Lambda Engine<br>
would automatically handle database server configuration, DNS setup,<br>
and so on.<br>
<br>
At the other extreme, we could simply provide a set of shell scripts<br>
for setting up a vanilla Ubuntu (or Debian, or Cent, or FreeBSD...)<br>
install to support compiling a WAI application, provide an nginx<br>
setup, etc. The user would be responsible- and have the freedom to-<br>
set up his/her own server however he/she wants.<br>
<br>
There are lots of in-between points on that spectrum. For example, I<br>
was thinking of perhaps providing a central compilation server that<br>
everyone could use. In my experience, Haskell applications take very<br>
few resources to run, but actually building the things take a while.<br>
Compiling on a local system and then uploading is painful because (1)<br>
you have to deal with architecture issues and (2) you might have a<br>
slow upload speed.<br>
<br>
Anyway, I'm very interested to hear what other people think about all<br>
this. I'll enumerate a bunch of random thoughts on this topic:<br>
<br>
* Should this be a for-profit venture, bankrolled by a few members, or<br>
a community, non-profit approach? (I'm favoring the latter.)<br>
* If we decide to provide some serious hosting power, we might be able<br>
to make a deal with a hosting provider, stating that we're<br>
representing the "entire Haskell web community".<br>
* I don't really think this needs to be WAI specific: assuming we just<br>
use reverse HTTP proxies, this will work for any app that uses<br>
standalone hosting. We could also support FastCGI if we wanted.<br>
* Remember that Amazon is now providing a free tier, which provides a<br>
micro EC2 instance (available as either 32 or 64 bit). I think the<br>
micro instance should be sufficient for running a few web apps, nginx<br>
and PostgreSQL.<br>
* Since starting up and shutting down instances is so easy with<br>
Amazon, we could provide both a "web host" image and a "Haskell<br>
compiler" image. The web host could automatically start up a compiler<br>
instance as needed.<br>
* Are we going to provide email sending support, with all of the<br>
complications of dealing with spam lists, or simply offload to<br>
external services (like Amazon SES[2])?<br>
* Does anyone have a good recommendation on who to use as a host?<br>
<br>
Michael<br>
<br>
[1] <a href="http://heroku.com/" target="_blank">http://heroku.com/</a><br>
[2] <a href="http://aws.amazon.com/ses/" target="_blank">http://aws.amazon.com/ses/</a><br>
<br>
_______________________________________________<br>
web-devel mailing list<br>
<a href="mailto:web-devel@haskell.org" target="_blank">web-devel@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/web-devel" target="_blank">http://www.haskell.org/mailman/listinfo/web-devel</a><br>
</blockquote></div><br></div></div>
</div></div>