##// END OF EJS Templates
When a specific TimeEntryActivity are change, associated TimeEntries will be...
When a specific TimeEntryActivity are change, associated TimeEntries will be re-assigned to the correct record. * Renamed build to create since the methods now create objects. * Removed call to Project#save that isn't needed since objects are saved directly now. * Wrapped the activity creation and updates in a SQL transaction so TimeEntries will remain in a consistent state if there is an error. * When a Project's TimeEntryActivities are destroyed, they are now reassigned to the parent TimeEntryActivity. #4077 git-svn-id: svn+ssh://rubyforge.org/var/svn/redmine/trunk@2950 e93f8b46-1217-0410-a6f0-8f06a7374b81

File last commit:

r761:b64e89daec8f
r2836:37d401ac58c3
Show More
production.rb
22 lines | 846 B | text/x-ruby | RubyLexer
# Settings specified here will take precedence over those in config/environment.rb
# The production environment is meant for finished, "live" apps.
# Code is not reloaded between requests
config.cache_classes = true
# Use a different logger for distributed setups
# config.logger = SyslogLogger.new
# Full error reports are disabled and caching is turned on
config.action_controller.consider_all_requests_local = false
config.action_controller.perform_caching = true
# Enable serving of images, stylesheets, and javascripts from an asset server
# config.action_controller.asset_host = "http://assets.example.com"
# Disable delivery errors if you bad email addresses should just be ignored
config.action_mailer.raise_delivery_errors = false
# No email in production log
config.action_mailer.logger = nil