Not exactly the same, but you can use BitNami and the AWS free tier (disclaimer, I am a developer) to deploy Wordpress with one click

http://bitnami.org/stack/wordpress#cloudImage

As Heroku has a Postgres backend, I imagine you could also install PG4WP (http://www.hawkix.net/tag/pg4wp/) which is a plugin to get Wordpress working with Postgres DBs, and just deploy directly using Heroku alone.

You may run into problems with any other plugins which use MySQL specific SQL syntax though.

It would be very interesting to see how something like this compares to running Wordpress at http://wpengine.com

wpengine sounds really expensive. $49/month for just 50k pageviews. My $39/month Linode setup handles a million page views with no sweat.

That is not a very good comparison, linode as you know does not provide the same feature set nor does it have WordPress devs on hand to help.

Even so, $49 a month is a LOT of money for not that much.

No, but you can pay someone $100 to install it for you and more or less forget it afterwards (since even WP version updates are mostly automatic from the admin UI --and even themes can be installed that way now).

Or, even better, use a Linode image with WP already installed, boot it and you're in business.

Heroku has addons (which are pretty fundamental to the system - even 'custom domains' is an addon, albeit first-party) which provide MySQL - it's even stated in the article...

For $70 a month, and it's not available to most people. Do your own fact checking.

http://evening-beach-7140.herokuapp.com/ # This is my install steps ( Install Wordpress on Heroku )

You guys seem to ignore the fact the Mysql addon costs $70/month on Heroku.

This is killer for small wordpress sites. You essentially get free custom domain hosting until it hits a traffic level where it needs something more significant, then you can re-evaluate your options.

You could also use git-svn to checkout the latest release branch:

http://core.svn.wordpress.org/tags/3.2.1

and then deploy to Heroku directly using git.

One of WordPress's devs maintains a WordPress github updated every 30 minutes, so even easier.

https://github.com/markjaquith/WordPress

This is cool, I'd wonder how many wordpress plugins are prepared to work with a read-only filesystem.

On the Cedar stack, the slug is still read-only, but the ephemeral filesystem is writable. The slug is what gets deployed on each new dyno spawned. The ephemeral filesystem is the individual file system on each dyno. So a plugin like WP Super Cache would be able to write to the file system, but that cache would only exist for the individual dyno that wrote it.

the cedar stack has a writeable file system, though no persistence across dyno recycles/restarts.

Plugins and themes cannot currently be installed through /wp-admin due to the PHP not having a zlib extension. Installation via git works fine though.

With Heroku you can only write to /tmp from your app.

This is great but, whats the best way to store attachments ?

You could use a WP plugin that stores them on Amazon S3. It's not free, but it's like < $1 month for normal blog needs.

The only plugin available explicitly states (on the Settings page, after you install and avtiavate it) that it doesn't upload directly to S3. It has to upload to your server first.

edit: actually, I think the upload to S3 button is different from upload media button. That's why I didn't see it.