unpacking tarball on existing website, in subdirectory or www

Previous topic

Install & configuration

Next topic

Author	Message
Paul VandenBosch	Thursday 23 October 2003 9:28:29 am I have an existing website and would like to add a ezpublish website in a subdirectory. Should I unpack the tarball in the www directory (public html) or should unpack it in a subdirectory? Is there anything else I should know to avoid damaging my existing website? Thanks
Balazs Halasy	Thursday 23 October 2003 11:16:43 am When unpacking an eZ publish tar.gz file using the tar archiving utility, you will automatically get a subdirectory into where eZ publish is unpacked. There is no need to create a dedicated directory. You may also rename the directory that eZ publish was put into. Example: allman@matrix:~$ cd public_html/ allman@matrix:~/public_html$ ls css my_imaginary_girlfriend index.html stuff allman@matrix:~/public_html$ wget http://ez.no/[..]ezpublish-3.2-2.tar.gz allman@matrix:~/public_html$ ls css ezpublish-3.2-2.tar.gz my_imaginary_girlfriend index.html stuff allman@matrix:~/public_html$ tar zxf ezpublish-3.2-2.tar.gz allman@matrix:~/public_html$ ls css ezpublish-3.2-2 ezpublish-3.2-2.tar.gz my_imaginary_girlfriend index.html stuff allman@matrix:~/public_html$ rm -f ezpublish-3.2-2.tar.gz allman@matrix:~/public_html$ mv ezpublish-3.2-2 cool_thing allman@matrix:~/public_html$ cd cool_thing allman@matrix:~/public_html/cool_thing$ ls LICENSE access.php design ezpublish.cron lib settings update PROFESSIONAL_LICENCE bin doc index.php pre_check.php share var README.txt cronjobs ezpm.php kernel runcronjobs.php support webdav.php

Author

Message

Paul VandenBosch

Thursday 23 October 2003 9:28:29 am

I have an existing website and would like to add a ezpublish website in a subdirectory.

Should I unpack the tarball in the www directory (public html) or should unpack it in a subdirectory?

Is there anything else I should know to avoid damaging my existing website?

Thanks

Balazs Halasy

Thursday 23 October 2003 11:16:43 am

When unpacking an eZ publish tar.gz file using the tar archiving utility, you will automatically get a subdirectory into where eZ publish is unpacked. There is no need to create a dedicated directory. You may also rename the directory that eZ publish was put into.

Example:

allman@matrix:~$ cd public_html/

allman@matrix:~/public_html$ ls
css
my_imaginary_girlfriend
index.html
stuff

allman@matrix:~/public_html$ wget http://ez.no/[..]ezpublish-3.2-2.tar.gz

allman@matrix:~/public_html$ ls
css
ezpublish-3.2-2.tar.gz
my_imaginary_girlfriend
index.html
stuff

allman@matrix:~/public_html$ tar zxf ezpublish-3.2-2.tar.gz

allman@matrix:~/public_html$ ls
css
ezpublish-3.2-2
ezpublish-3.2-2.tar.gz
my_imaginary_girlfriend
index.html
stuff

allman@matrix:~/public_html$ rm -f ezpublish-3.2-2.tar.gz

allman@matrix:~/public_html$ mv ezpublish-3.2-2 cool_thing

allman@matrix:~/public_html$ cd cool_thing

allman@matrix:~/public_html/cool_thing$ ls
LICENSE
access.php
design
ezpublish.cron
lib
settings
update
PROFESSIONAL_LICENCE
bin
doc
index.php
pre_check.php
share
var
README.txt
cronjobs
ezpm.php
kernel
runcronjobs.php
support
webdav.php

eZ debug

Timing:	Jan 18 2025 19:30:31
Script start
Timing:	Jan 18 2025 19:30:31
Module start 'layout'
Timing:	Jan 18 2025 19:30:31
Module start 'content'
Timing:	Jan 18 2025 19:30:31
Module end 'content'
Timing:	Jan 18 2025 19:30:31
Script end

Main resources:

Total runtime	0.7880 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0064	588.3984	152.6875
Module start 'layout'	0.0064	0.0028	741.0859	39.5234
Module start 'content'	0.0093	0.7775	780.6094	504.5547
Module end 'content'	0.7868	0.0012	1,285.1641	8.0781
Script end	0.7880		1,293.2422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.4334	16	0.0002
Check MTime	0.0014	0.1789	16	0.0001
Mysql Total
Database connection	0.0010	0.1216	1	0.0010
Mysqli_queries	0.7296	92.5960	54	0.0135
Looping result	0.0005	0.0638	52	0.0000
Template Total	0.7493	95.1	2	0.3747
Template load	0.0036	0.4566	2	0.0018
Template processing	0.7457	94.6392	2	0.3729
Template load and register function	0.0001	0.0187	1	0.0001
states
state_id_array	0.0014	0.1715	1	0.0014
state_identifier_array	0.0020	0.2500	2	0.0010
Override
Cache load	0.0032	0.4044	57	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0741	2	0.0003
Fetch class attribute name	0.0013	0.1693	3	0.0004
XML
Image XML parsing	0.0007	0.0906	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0010	3	0.0000
General
dbfile	0.0008	0.1061	16	0.0001
String conversion	0.0000	0.0010	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs