File system architecture and distribution idea

« 
Previous topic
|
Suggestions
|
Next topic
 »
Author Message

Betsy Gamrat

Monday 11 August 2008 3:57:55 pm

It may be good to consider changing the file system architecture of eZ to allow distribution of eZ through RPMs. By moving those directories most commonly customized/used/modified (settings, design, extension, var) from the eZ tree, the eZ core could be installed with one RPM, and a script provided that would copy the defaults for the settings, design, extension, var directories into DocumentRoot of the sites. This would allow the eZ core to be managed as an RPM, while ensuring the flexibility is not lost. A single eZ installation could support an entire server, each site would symlink to the core, and customize the remaining elements.

Each site would be entirely independent of the others, they would have separate databases.

Maxime Thomas

Tuesday 02 September 2008 11:17:19 pm

Hi,

I know that is maybe a Linux lover point of view but I guess clients of eZSystems partner would also use http servers like IIS. So, what about a RPM ?

:-/

Maxime Thomas
maxime.thomas@wascou.org | www.wascou.org | http://twitter.com/wascou

Company Blog : http://www.wascou.org/eng/Company/Blog
Technical Blog : http://share.ez.no/blogs/maxime-thomas
Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 04:24:15
Script start
Timing: Jan 18 2025 04:24:15
Module start 'layout'
Timing: Jan 18 2025 04:24:15
Module start 'content'
Timing: Jan 18 2025 04:24:15
Module end 'content'
Timing: Jan 18 2025 04:24:15
Script end

Main resources:

Total runtime0.5049 sec
Peak memory usage4,096.0000 KB
Database Queries54

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0056 589.1797152.6406
Module start 'layout' 0.00570.0027 741.820339.4766
Module start 'content' 0.00840.4949 781.2969531.7266
Module end 'content' 0.50330.0016 1,313.02348.1250
Script end 0.5049  1,321.1484 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00340.6682160.0002
Check MTime0.00140.2845160.0001
Mysql Total
Database connection0.00100.189710.0010
Mysqli_queries0.458290.7564540.0085
Looping result0.00050.0976520.0000
Template Total0.475694.220.2378
Template load0.00240.476320.0012
Template processing0.473293.708920.2366
Template load and register function0.00010.028110.0001
states
state_id_array0.00080.166210.0008
state_identifier_array0.00110.218020.0006
Override
Cache load0.00200.4020110.0002
Sytem overhead
Fetch class attribute can translate value0.00060.110720.0003
Fetch class attribute name0.00130.249240.0003
XML
Image XML parsing0.00200.405920.0010
class_abstraction
Instantiating content class attribute0.00000.001440.0000
General
dbfile0.00160.3147220.0001
String conversion0.00000.001740.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
2content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
2content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
2content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 8
 Number of unique templates used: 5

Time used to render debug report: 0.0002 secs