> For the simple experiments I've done on Heroku, I've typically kept my > auto-generated taglibs as part of my GIT repository and insured they are are > up to date before pushing to Heroku, otherwise Hobo will try to regenerate > them (which it can't do in Heroku's read-only file system.) >
More or less :-) You actually don't need to set config.hobo.read_only_file_system = true explicitly anywhere, if your app will run on heroku, because it will be automatically detected and set to true for you. When it is true hobo will not try to generate any file (auto taglibs, and hobo_routes). In that case you have to provide the files to heroku: a) by including them in your repo (there is an option that you can choose in the setup_wizard that will add the files to the repo) OR b) uploading them in any other way ciao dd -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
