bacongobbler

There are a couple other PaaS options as well coming in the near future. For open source options that are currently in development, there's https://flynn.io/ and http://deis.io/. For production-ready Enterprise private PaaS (meaning that you host the PaaS on your own hardware) that are currently ready for production use, there's Stackato (http://www.activestate.com/stackato), OpenShift (https://www.openshift.com/), and Cloud Foundry (http://www.cloudfoundry.com/).

If you're just looking to deploy a single application on Digital Ocean or some other VPS, the digitalocean plugin for knife will really help out (https://github.com/rmoriz/knife-digital_ocean).

EDIT: In regards to Stackato...

-- (1) command-line client for deployment via git repository and doing anything related to deployment (add new instances, remove instances, create new environments, assign domains to the PaaS router, etc.)

We have a CLI for doing this, as well as a web API and a Python library for communicating with the API (see https://github.com/bacongobbler/python-stackato)

-- (2) clear pricing

We have a clear memory-based pricing plan. This allows users to scale out their infrastructure to as many nodes as they like, and only have to manage their total memory in their clusters to figure out pricing.

-- (3) I can pay for more memory as I need it

It's on your own hardware. EC2/Rackspace/VMWare pricing depends on their model.

-- (4) ability to specify environment variables in a configuration file that take effect on the container process

We have a couple of default env vars in the application container, as well as letting users configure their own envvars. See http://docs.stackato.com/reference/environment.html and http://docs.stackato.com/reference/stackatoyml.html

-- (5) web interface for administering the account

We have both the CLI, the API, and a web interface. Check out our YouTube channel at http://www.youtube.com/user/ActiveStateSoftware for tutorials around the Stackato console, or just take a look at http://docs.stackato.com/ :)

Disclaimer: I work as a product manager for ActiveState, working on Stackato. We'd love to have you over here! We're also on Freenode, channel #stackato if anyone is interested in this stuff :)

Digital Ocean and Rackspace provider support is coming soon. See https://github.com/opdemand/deis/issues/121 and https://github.com/opdemand/deis/issues/73

TIL. Thanks for the heads up.

possible? yes. The better question you should ask yourself would be "does the use case make sense?"

Linux containers are ephemeral, which means that you will lose all data from your email server on a container restart. If you're just setting up a postfix SMTP server in a container, and forwarding the guest's port 25 to the host, I don't see why not. You probaby won't have any app scaling support or the likes, though. I could be wrong about that. I've never attempted to set up a clustered SMTP server configuration before.

How does this engine handle updating? From looking at the source, I could see that it caches the gists in Mongo, but what happens if you introduce a typo into your gist? Wouldn't it just keep serving the old post until you clear Redis and delete the entry in Mongo?

Looks interesting, but I still love me some jekyll with automated deployments through git-receive hooks.

You can always read the README on GitHub. no markup there.

https://raw.github.com/balderdashy/sails/master/README.md

If you want to install npm for user-specific installations (such as when you don't want to require root access when installing an npm module, or that the computer is shared), you can download the NodeJS tarball, and run

    ./configure --prefix=/home/user/local

Which should install into your ~/local directory after running 'make && make install'.