First off, it was friggin' amazing to run through the sample workflow and have a new version controlled live Rails app in seconds.
Is there a bug tracker or anything like that where we should report odd behavior? I'd hate to re-report errors that other people have experienced, or just generically spam this list with random errors. But I will if I have to! :) I received the "remote end hung up" error that has been reported, you can see the full error here: http://pastie.caboo.se/161518 I then went through the procedure with a brand new application created through "heroku create" and it worked fine. After playing around with that, I went back and tried to clone the application that I had created via the web interface, and it worked fine... Also, I noticed that most of the scripts for both applications are not set to be executable. I'd imagine that's by design on your end, but it's a mild annoyance on my local system. Either way congratulations, this is awesome. Don On Mar 1, 3:04 pm, "Adam Wiggins" <[EMAIL PROTECTED]> wrote: > One of our most-requested features has been the ability to combine > existing local development environments with deployment on Heroku. As > a lot of you may already know, we've put together an API and external > access to revision control (usingGit) to allow just this. We've got > a full announcement, including a screencast, coming to the blog on > Monday. But the gem has already propagated on RubyForge, so if you're > a current Heroku user, you can start using this now. On your local > system, run: > > sudo gem install heroku > > You can then run "heroku list" to get a list of your apps, and "heroku > clone <app>" to pull down a copy to work locally. Full docs can be > found here: > > http://heroku.com/docs/api/ > > To take full advantage of this, you will need not only a full working > Rails environment, but alsoGit, and an ssh public key. For this time > being this will probably only work in a unix environment, i.e. OS X, > Linux, or *BSD. Windows + Cygwin will probably work too. > > Note that once you upload your public key (done automatically when the > credentials are sent), all your apps will be activated for revision > control. There's a Revisions link in the lefthand filenav; as you > make changes in the Heroku web editor, you'll need to commit them in > order to access them externally. (Revisions will become standard for > all Heroku apps in the near future, regardless of external access.) > > We're looking forward to hearing your experiences with working locally > and deploying to Heroku (or combining local development and working in > the web editor), so please post here with your comments and criticisms > once you've had a chance to try it out. > > Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
