Heroku runs on ec2, no? What prevents exposure of an EBS block to an app? On Tue, Oct 6, 2009 at 5:32 PM, Oren Teich <[email protected]> wrote: > > Hi Neil, > There aren't any plans for shared storage right now. I wish I could > say otherwise. The big challenge is that we're able to achieve our > scaling and overall cool features by imposing certain constraints. A > read-only file system is one of those. If we had a shared filesystem, > we wouldn't be able to offer the scalability or performance that makes > our platform so unique. There are some interesting plugins that some > 3rd partys have in development that will capture filesystem requests > and send them to S3 instead. Hopefully as these come out they might > help address some of the constraints for you. > > Believe me, I wish we could figure out a way to give you a writeable > filesystem! > > Good luck, > Oren > > On Oct 6, 2009, at 2:53 AM, Neil wrote: > >> >> One of the big issues we have with Heroku as a business at the moment >> is the read-only file system and the fact that this then renders some >> of our legacy apps, and our CMS of choice, BrowserCMS, unable to be >> deployed without some serious hacker-age. >> >> Question is, are there any plans at all for some sort of shared >> storage, where I can somehow define a directory or two that should be >> shared across all dyno's serving my application, as well as across all >> deploys of my application? >> >> For me, this is a major thing, and it would be good to remove one of >> the big barriers that people might have. >> > > > > > >
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
