Forget RubyForge and SourceForge and Valley Forge (oops you already did), say hello to my little friend... Heroku !!!
After I got my first "blessed" app into production, it really began to dawn on me just how powerful and game-changing Heroku is. I had a "Heroku moment" just now while writing a blog post. I think it is a killer idea and I hope you agree, here is an excerpt from my post... Here’s a really cool idea, ever hear of Heroku? Heroku is a full- stack Ruby on Rails development tool… completely web-based (including code editing, database management, testing, and production environment)!! Heroku would be the perfect place for Gem/Plugin developers (or really good blog writers) to drop a complete working example!! No need to document the long migrations involved just to get a database setup for a working sample. You could simply create a new Rails project at the Heroku web site, upload the code and database from your computer to Heroku, and make the link to your app “Public”. This is a completely cool solution to the age-old problem of having sample applications that you can run and view the code without having to download/install anything! The only thing currently making this an imperfect solution is that to see the code, database, logs, etc. Heroku requires that each person be setup as a “contributor” on the project. Maybe the good folks at Heroku can work something out for this type of usage… So, here I am asking if you guys can work something out to accomplish this. Perhaps there could be a subdomain of Heroku called "Community". Instead of just being a code repository, Heroku "Community" could be home to a living breathing on-line development community. Even if developers and bloggers just had a place to set up a public demo where everybody could "view" the code, databases, logs, and could grab an export... all in real-time. That would be so amazing!!! How many times have I seen a great blog post with some really cool Rails application idea, followed by pages of instructions for setting up a sample, and migrating a complete database that will never be used for anything other than to see the code properly applied to an application and functioning. Now, imagine blogging about how you are creating some new Rails Gem. You blog about what it does, include some code snippets and a screenshot for the discussion, and then you just provide a link to the Heroku Community app where any interested developer can run your fully functional sample app, poke around behind the curtain (read-only access) to see the code, folder structure, scripts, etc. as they exist in a fully functioning site. The developer could then grab an "export" copy for download. Or, if they already have a Heroku account, they could hit the special "Copy this app to My Apps" button. My full post is at http://oomoo.wordpress.com/2008/08/26/rails-blogs-make-me-feel-stupid/). I am working on a "Heroku is the future of development" post that should be coming out soon :) So, what do you think? Thank You! Paul James --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
