Ticket #213 (new enhancement)

Opened 3 years ago

Last modified 3 years ago

Integration with other TigerProjects

Reported by: cjordan Assigned to: somebody
Priority: normal Milestone: WishList
Component: General Version: HEAD
Severity: normal Keywords:
Cc:

Description (Last modified by ssmith)

As TigerProjects? are intended to eventually be a product suite, we should make sure that they integrate with each other. However, as the entire suite is not necessarily needed for all instances, case must also be taken to ensure they can be used independently.

Change History

13/09/05 06:21:28 PM changed by ssmith

  • version set to HEAD.
  • milestone changed from 1.20 to WishList.

Putting into wishlist until TigerSociety? is written.

12/10/05 03:38:49 PM changed by ssmith

  • description changed.
  • summary changed from Integration with "TigerSociety" to Integration with other TigerProjects.

12/10/05 03:45:24 PM changed by ssmith

Potentially, we should seperate config files into seperate files.

For example, we have TigerEvents? and TigerBooks? working together. The following config files would be used:

tigercore_config.rb (handles authentication type, LDAP settings, admin mail, etc). tigerevents_config.rb (handles TigerEvents? specific settings) tigerbooks_config.rb (handles TigerBooks? specific settings).

Also, you could include code like this in tigercore_config.rb 

require 'tigerevents_config' if File.exist?('tigerevents.config.rb')
require 'tigerbooks_config' if File.exist?('tigerbooks.config.rb')