Ok, I tested this further by running Thin locally. Thin running on my system *never* calls the scripts in config/initializers more than once, at startup (even in development mode).
Please, if you have any idea what causes Heroku to behave in this way (calling the initializers up to four times at startup time, and sometimes at random times while the app is running), let me know if this is a bug or if I need to take special precautions. This is my only beef with heroku at the moment, and my app is ready for testing once this is resolved. I'm reluctant to try out various tricks to make this work before I have confirmed whether this is behavior that could be classified as a bug on Heroku's part or not. Any feedback would be very much appreciated. /Felix 2009/2/24 Felix Holmgren <[email protected]>: > Hi! > > I just found out that my initializers (in config/initializers) get > called four (4!) times when I run "heroku restart". . . . --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
