Changeset 1008 in ExiteCMS
- Timestamp:
- 10/24/07 10:23:06 (4 years ago)
- File:
-
- 1 edited
-
README.TXT (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
README.TXT
r874 r1008 2 2 | ExiteCMS - Web Development Project | 3 3 | | 4 | (c) 200 7 Harro "WanWizard" Verton - Exite BV|4 | (c) 2006-2007 Exite BV, Rotterdam, The Netherlands | 5 5 | Portions (c) 2004-2006 Nick "Digitanium" Jones | 6 | | 7 | For support, go to http://exitecms.exite.eu | 6 8 | | 7 9 | ExiteCMS is released under GPL v2 | … … 65 67 66 68 When you want to install the code from SVN, use this sequence: 67 * first, install the core code 68 * second, install the common modules 69 * first, install the core code (from trunk or branch) 70 * second, install the common modules (only the ones required) 69 71 * third, install the common theme (if needed) 70 72 * forth, install any modules specific for the branch (if any) 71 73 * fifth, install any themes specific for the branch (if any) 72 74 73 Especially for branch developments this sequence is important, 74 because there could be branch specific core code that must overwrite 75 the original code from the trunk or common code. 76 77 The SVN administrator has linux scripts that can assign in keeping 78 a specific web environment up to date from SVN. Contact the 79 administrator for more information. 75 The SVN administrator has some bash scripts that can assign in 76 keeping a specific web environment (usually a staging site) in 77 sync with the commits into the SubVersion repository. 78 Contact the administrator for more information. 80 79 81 80 The rights on SVN are setup in such a way that every authorized
Note: See TracChangeset
for help on using the changeset viewer.
