Dr Nic Williams

Oh no. Hmm, I wonder how to reproduce that locally. I'll try later. Would you like to try upgrading to latest ruby 1.9.3 also and see if that resolves it?...

I'll look to test & include this in next release

To bring in a new target deployment host (Heroku, CF, etc), we need to ensure that appscrolls works as expected - prevent scrolls that aren't applicable (mysql on heroku?), and...

Hmm, good question. Something related is that 'eycloud' scroll requires that you have one of the SQL DB scrolls and one of the app server scrolls https://github.com/drnic/appscrolls/blob/master/scrolls/eycloud.rb#L9-23 'heroku' scroll could...

The behavior from "exclusive: orm" is in http://github.com/intridea/rails_wizard.web. I don't think it currently has a meaning in rails_wizard/appscrolls CLIs. I could do though - perhaps show a warning or error?

I think the bulk of the work will be in generating the correct Procfile. Should be easy - a scroll appends a line to the Procfile for its process (resque...

If we can control the onboarding experience then we can setup a cedar stack for them. Why not do that? Is bamboo stack better?

Right; cedar isn't just about procfiles; its also a normal, old fashioned stack update. I'm interested to start a "should we encourage/force ruby 1.9 for new apps" conversation too later.

Status: I started a heroku branch with @hone. So far, a procfile scroll was added. The heroku scroll hasn't been upgraded to cedar; nor do any scrolls contribute the Procfile...

Great! I'll test it out soon!