Our only niggle is with the CMS we use for a few sites (BrowserCMS). This CMS uploads to the local filesystem and uses cache_page for page caching. Although I've created a patch for this which diverts uploads to S3, and sticks a 500s cache header on each page, it's still not as nice as knowing that the change has been made at a lower level.
N On Oct 14, 1:59 pm, Chap <[email protected]> wrote: > Neil, can I ask what kind of stuff you need the filesystem for? > > I too thought this would be a show stopper, but after a few months of > just using S3 I can honestly say I don't want to go back to the > filesystem. > > I'm not doing anything crazy, importing some big CSV's, generating and > saving some big PDF's. I had to change my approach to these, but in > the end I think it was worth it. > > On Oct 14, 6:00 am, Neil <[email protected]> wrote: > > > Do you have links to any of these plugins at all or is it still to > > early? > > > N > > > On Oct 6, 10: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 -~----------~----~----~----~------~----~------~--~---
