Jump to: navigation, search

Umlaut Local Configuration Architecture

1,492 bytes added, 16:20, 15 June 2009
Reverted edits by (Talk); changed back to last version by
hlkXFU <a href="http:= Principles//mvzvucuxzrszGoals: == # Ideally you will not need to edit the common Umlaut codebase to make purely local">mvzvucuxzrsz</All local customizations should occur via various types of configuration options, with the common Umlaut codebase being untouched - except with changes of wider applicability you submit back to the common codebase.# This means any code or config for local customization will ideally be kept clearly distinct from the common codebase.# If you like, you should be able to keep any of your local code or config files in your own local SVN or CVS repository, while at the same time getting shared codebase Umlaut code from the central Umlaut repository, combined together in a>working Umlaut installation. (You might or might not want your production Umlaut to be an SVN working copy, [url=httpbut if you are a developer you will certainly want your development copy to be!) To accomplish this required doing things a tiny bit different than standard Rails. ://kjerqjirdlka''We realized after the fact that the Rails Engines plugin might be a great solution to those Goals, requiring less that's 'not the Rails way', and may explore refactoring Umlaut to be an Engines]kjerqjirdlka[/url]But hasn't happened yet.'' Where in a normal Rails app you would customize various files in the config directory, [link=http:/in Umlaut the files in the config directly have common Umlaut configuration necessary for any Umlaut environment, but your local config is instead in files in config/]agejeoovcngk[/link] There are files used in umlaut_config that look very much like the standard Rails config files (eg database.yml, http://hligaxaxlfafenvironment.rb), and also some Umlaut specific ones (eg services.yml, institutions.yml).com/
== Directory Locations For Local Content ==

Navigation menu