eZ publish distribution with eZ flow / eZ webin packages

Next topic

Author	Message
Thiago Campos Viana	Friday 10 September 2010 12:14:32 pm I was thinking, the step that could cause a php max execution time error, in most cases, is when eZ publish starts to download the packages that the user choosed. So I suggest to distribute eZ publish with all packages needed to make an eZ Flow / eZ Web Interface with content installation, this could be a flawless distribution that could include zeta components ( ez components ) too. So, the installation could be quicker. I think it could also minimize ez.no bandwich, because doing so, it will not be necessary to download all packages from ez.no every installation, we could just unzip and voilà! We have all we need to make the basic installation. eZ Publish Certified Developer: http://auth.ez.no/certification/verify/376924 Twitter: http://twitter.com/tcv_br
SEBBANE Alexandre	Saturday 18 September 2010 8:38:48 pm Hello, i was thinking exactly like you when i found the example which make me change my mind : the first is that you can also make your import as in the exrowecommerce project : [RepositorySettings] RemotePackagesIndexURL=http://packages.xrow.com/xrowecommerce/latest RemotePackagesIndexURLBase= and the second reason is that if you know how many packages are docnload you know as well how many installation is made so it is important for ezsystems i think Bye Alex Paris, France

Author

Message

Friday 10 September 2010 12:14:32 pm

I was thinking, the step that could cause a php max execution time error, in most cases, is when eZ publish starts to download the packages that the user choosed. So I suggest to distribute eZ publish with all packages needed to make an eZ Flow / eZ Web Interface with content installation, this could be a flawless distribution that could include zeta components ( ez components ) too. So, the installation could be quicker. I think it could also minimize ez.no bandwich, because doing so, it will not be necessary to download all packages from ez.no every installation, we could just unzip and voilà! We have all we need to make the basic installation.

eZ Publish Certified Developer: http://auth.ez.no/certification/verify/376924

Twitter: http://twitter.com/tcv_br

SEBBANE Alexandre

Saturday 18 September 2010 8:38:48 pm

Hello,

i was thinking exactly like you when i found the example which make me change my mind :

the first is that you can also make your import as in the exrowecommerce project :

[RepositorySettings]
RemotePackagesIndexURL=http://packages.xrow.com/xrowecommerce/latest
RemotePackagesIndexURLBase=

and the second reason is that if you know how many packages are docnload you know as well how many installation is made so it is important for ezsystems i think

Bye

Alex

Paris, France

eZ debug

Timing:	Jan 18 2025 04:13:43
Script start
Timing:	Jan 18 2025 04:13:43
Module start 'layout'
Timing:	Jan 18 2025 04:13:43
Module start 'content'
Timing:	Jan 18 2025 04:13:43
Module end 'content'
Timing:	Jan 18 2025 04:13:43
Script end

Main resources:

Total runtime	0.0144 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	589.2734	152.6563
Module start 'layout'	0.0054	0.0030	741.9297	39.5078
Module start 'content'	0.0084	0.0044	781.4375	89.3984
Module end 'content'	0.0128	0.0015	870.8359	30.3047
Script end	0.0143		901.1406

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	17.7218	14	0.0002
Check MTime	0.0012	8.3336	14	0.0001
Mysql Total
Database connection	0.0007	4.6261	1	0.0007
Mysqli_queries	0.0017	11.8637	3	0.0006
Looping result	0.0000	0.0763	1	0.0000
Template Total	0.0013	8.9	1	0.0013
Template load	0.0007	4.6874	1	0.0007
Template processing	0.0006	4.2282	1	0.0006
Override
Cache load	0.0004	3.1288	1	0.0004
General
dbfile	0.0003	1.7891	8	0.0000
String conversion	0.0000	0.0547	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs