On 6/15/07, Michael Koziarski <[EMAIL PROTECTED]> wrote: > > In the case of two environments that share common pieces of code, > > absolutely. Where I've found this most useful, though, is in a case > > where an environment is either *precisely* the same as another (except > > for the database, e.g., running with a copy of live data on your local > > dev machine), or differs in the most minor of ways. > > Couldn't you achieve this with symlinks though?
Absolutely. The only reason I can think of to use something like my acts_like sugar instead of symlinks is clarity and maintainability over time: I think it's good that anybody who cats/edits the file will immediately know that it mirrors another environment, which isn't necessarily the case with a symlink. We're all moving at lightspeed 'round here, and the more explicit information the better. Symlinks aren't sneaky, but they're certainly not always obvious. That said, the combination of initializers and symlinks makes my justification pretty thin. :) ~ j. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
