No... thank you Adam!  You guys are doing a great job!

Although I have to post my source code on my FTP site, I can still use
Heroku to host fully-functioning demos of techniques that I blog
about.

For example my post 
http://oomoo.wordpress.com/2008/08/20/how-do-i-refresh-individual-form-fields/
has links at the bottom encouraging people to try out a real live copy
of the application (a free Outlook signature generator application in
this case).  And of course, the obligatory plug for Heroku ;}

So, the current Heroku architecture can get me half the way to where I
want to go.  Of course, you could have a "public" Heroku login, then
anybody wishing to allow public access to the source code of an app
could just invite the public login.  I know... that would be a big
security problem, I'm just thinking out loud here :)  That scenario
would work if we had the option to allow a collaborator to have read-
only access to the source/data/logs.  Then there wouldn't be any
security issues.

Well, as soon as you get done with all your boring stabilizing crap
(humor), let me know!

Thanks,
Paul James


On Aug 28, 4:00 pm, "Adam Wiggins" <[EMAIL PROTECTED]> wrote:
> Thanks Paul, we're glad you like Heroku so much.
>
> I totally agree that the possibilities for broader collaboration are
> really exciting - we have tons of ideas for this, some of which are
> already in the works.  At the moment we're mostly focused on
> stabilizing the platform, but we're really looking forward to being
> able to work on collaboration and other advanced features in the near
> future.
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to