Changeset 860 in ExiteCMS


Ignore:
Timestamp:
09/29/07 22:35:13 (4 years ago)
Author:
root
Message:

Updated readme text

File:
1 edited

Legend:

Unmodified
Added
Removed

  • README.TXT

    r837 r860  
    1 /------------------------------------\ 
    2 | ExiteCMS - Web Development Project | 
    3 |                                    | 
    4 | (c) 2007 Harro Verton - Exite BV   | 
    5 | Portions (c) 2004-2006 Nick Jones  | 
    6 |                                    | 
    7 | ExiteCMS is released under GPL v2  | 
    8 \------------------------------------/ 
     1/------------------------------------------------------------\ 
     2| ExiteCMS - Web Development Project                         | 
     3|                                                            | 
     4| (c) 2007 Harro "WanWizard" Verton - Exite BV               | 
     5| Portions (c) 2004-2006 Nick "Digitanium" Jones             | 
     6|                                                            | 
     7| ExiteCMS is released under GPL v2                          | 
     8\------------------------------------------------------------/ 
    99 
    1010This is the software repository of the ExiteCMS project.  
    1111 
    12 Exite also uses this SVN repository to manage the branches 
    13 or forks of the ExiteCMS main development train. 
    14 It is also used for development of specific modifications  
    15 to either the core code or modules, on request of it's 
    16 clients, and for client specific development. 
     12ExiteCMS is modeled on version 6 of the highly succesful lightweight 
     13CMS "PHP-Fusion", http://www.php-fusion.co.uk, by Nick Jones. 
     14 
     15Most of the code has been completely rewritten since we started 
     16with this project at the end of 2006, but we still like to give 
     17Nick Jones a big thanks for all the great work he did, and for 
     18'showing us the path'. 
     19 
     20Exite CMS uses the Smarty template engine (http://smarty.php.net), 
     21copyright The PHP Group inc, and released under LGPL v2. 
     22 
     23Exite uses this SVN repository not only for development of the 
     24ExiteCMS engine itself, but also to manage the branches or forks  
     25of the ExiteCMS main development train. 
     26 
     27Besides that, it is also used for development of specific  
     28modifications to either the core code or modules, on request  
     29of it's clients, and for client specific development. 
    1730 
    1831This SVN repository uses the following structure: 
    1932 
    20 /                           SVN root directory 
     33/                            SVN root directory 
    2134 
    22 /trunk                      main ExiteCMS development train 
     35/trunk                       main ExiteCMS development train 
    2336 
    24 /branches                   branches of the main train 
    25     /<client or site>       client or site specific core code 
    26                             or extensions to the core code 
     37/branches                    branches of the main train 
    2738 
    28 /modules                    optional CMS modules 
    29     /common                 ExiteCMS supplied modules 
    30     /<client or site>       client or site specific modules 
     39    /<client or site>        client or site specific core code 
     40                             or extensions to the core code 
    3141 
    32 /tags                       tagged releases 
    33     /ExiteCMS core          ExiteCMS core releases 
    34     /<client or site>       client or site specific releases 
     42/modules                     optional CMS modules 
    3543 
    36 /themes                     ExiteCMS custom designed themes 
    37     /common                 ExiteCMS supplied modules 
    38     /<client or site>       client or site specific themes 
     44    /common                  ExiteCMS supplied modules 
     45    /<client or site>        client or site specific modules 
     46 
     47/tags                        tagged releases 
     48 
     49    /ExiteCMS core           ExiteCMS core releases 
     50    /<client or site>        client or site specific releases 
     51 
     52/themes                      ExiteCMS custom designed themes 
     53 
     54    /common                  ExiteCMS supplied modules 
     55    /<client or site>        client or site specific themes 
     56 
     57When you want to install the code from SVN, use this sequence: 
     58* first, install the core code from either the trunk, tag or branch 
     59* second, install the common modules 
     60* third, install the common theme 
     61* forth, install any modules specific for the branch (if any) 
     62* fifth, install any themes specific for the branch (if any) 
     63 
     64Especially for branch developments this sequence is important, 
     65because there could be branch specific core code that must overwrite 
     66the original code from the trunk or common code. 
     67 
     68The SVN administrator has linux scripts that can assign in keeping 
     69a specific web environment up to date from SVN. Contact the  
     70administrator for more information. 
    3971 
    4072The rights on SVN are setup in such a way that every authorized 
Note: See TracChangeset for help on using the changeset viewer.