Hey Tracks users! I have some good news: no more environment.rb
headaches. After this one, that is. The next time you update from the
tracks core, it will likely overwrite your environment.rb without
asking you. Yeah, I know, that's less than optimal, but there's not
much I can do about git's behavior. The good news is that this is the
last time you'll need to edit your own environment.rb, and you don't
even need to edit it! Here are the steps you need to take to update:
1) move environment.rb to some place safe
2) git pull origin (or however you update)
3) Copy config/site.yml.tmpl to config/site.yml
4) Move your site-specific configuration from your environment.rb to
the settings in config/site.yml
5) Update deploy scripts appropriately
You're good to go! Now whenever we mess with environment.rb you'll
automatically be updated, and your site-specific configuration will
stay in site.yml. If you have other site-specific stuff that doesn't
fit into site.yml, please let me know. You can work around the
constraint by using config/initializers.
-Eric Allen
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
