Re: Config vars and local setup
On Jun 23, 11:47 pm, Trevor Turk wrote: > You can see the relevant files here: Apologies, but I (just) changed the repo name on github, so here are the new URLs: http://github.com/trevorturk/eldorado/blob/8af62d1875ec1091ef1202c3f8c6c58c932076d7/config/config.example.yml http://github.com/trevorturk/eldorado/blob/8af62d1875ec1091ef1202c3f8c6c58c932076d7/config/environment.rb http://github.com/trevorturk/eldorado/blob/8af62d1875ec1091ef1202c3f8c6c58c932076d7/lib/tasks/heroku.rake ...and... http://github.com/trevorturk/eldorado/tree/master Sorry about that! - Trevor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Config vars and local setup
I don't really like the suggested approach in the Heroku docs for setting config vars locally: http://docs.heroku.com/config-vars#local-setup I have an open-source project I'm working to get onto Heroku, so I decided to do some work and come up with a better solution (to my mind, anyway)... Here's the basic idea: You have a config/config.yml file that has all of your local config stuff. If looks a lot like database.yml. You have a little trickery in environment.rb to prefer the Heroku ENV style of setting config vars (in production), but you fall back to your config.yml if the config vars aren't found in ENV (in dev/test). Then, you have a rake task (rake heroku:config) that sends all of the config vars up to Heroku for use the production environment. That way, you've got all of your config vars stored with your project (.gitignored, of course), and can easily set what you need on Heroku. You can see the relevant files here: http://github.com/trevorturk/el-dorado/blob/8af62d1875ec1091ef1202c3f8c6c58c932076d7/config/config.example.yml http://github.com/trevorturk/el-dorado/blob/8af62d1875ec1091ef1202c3f8c6c58c932076d7/config/environment.rb http://github.com/trevorturk/el-dorado/blob/8af62d1875ec1091ef1202c3f8c6c58c932076d7/lib/tasks/heroku.rake The result is a pretty nice, I think. You can see the installation instructions here, if you're curious about the flow: http://github.com/trevorturk/el-dorado/tree/master I'd love to get some feedback on this strategy. I really like it so far :) Thanks, - Trevor --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Spam
I triple vote for that. I want to keep up to date on heroku, but the spam really sucks. On Tue, Jun 23, 2009 at 11:12 AM, Trevor Turk wrote: > > I've read elsewhere that setting the "first post by a user must be > approved by a moderator" thingy in Google Groups can really help with > spam... > > > -- Cheers --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Spam
I've read elsewhere that setting the "first post by a user must be approved by a moderator" thingy in Google Groups can really help with spam... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Anna Kournikova - Hot Photoshoot
Click Here to Watch This Video --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: A Vote for Supporting MySQL
I think I agree with the decision that the Heroku team took to support Postgresql only if thats what makes sense for them. One of the claimed selling points for Rails itself is that switching between databases is supposed to be trivial. Calling something a plugin implies that it is supposed to be generic enough to be reusable in many different environments (especially when we are talking about free database engines). If an author of a Rails plugin can't be bothered to verify compatibility with more than one database engine, then, IMHO, he's producing shoddy work, and I certainly don't think that the Heroku guys have to ensure that everyone's shoddy product has to work on their platform On Mon, Jun 22, 2009 at 9:55 PM, Brian Armstrong wrote: > > agreed, these are all viable workarounds...but really, you don't want > to add a caveat like "easy rails deployment - if you don't mind > editing SQL in some plugins" > > I guess there are some licensing issues going on with MySQL, so I > understand if it's not easy. > > On May 3, 7:06 pm, giorgio wrote: >> I agree that using searchval.downcase like lower(blah) works fine and >> I have been doing this since discovering that Postgres searches were >> case sensitve. >> >> However it is a pain and can still catch you out when you forget and >> of course it works fine in development. >> >> Having a different database in development/test and in production is a >> recipe for problems however I have not yet bit the bullet and >> installed postgres locally as it just seems like more complications >> when I have multiplemysqldatabases already. >> >> I would guess that more people usemysqlthan anything else. (but I >> could well be wrong!) >> >> Cheers >> george > > > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
