Pre install question

Next topic

Author	Message
Benj Duval	Sunday 19 March 2006 3:44:11 pm Hi, I finally decided to use Ez publish as it seems to be the ONLY cms to fits almost all my needs right out of the box. I currently have my site installed in /www/ . This is the web root. So when people go to www.mysite.com they see the index in there. This is where I want the eZ publish index. BUT.... it will take lots of time for me to setup the site, and convert all my content to ez publish and I don't want people to see my eZ index until I finished the work. So what is the best solution ? Should I install eZ publish in its own directory ? Is there an option to move the index in the root directory once i'm ready ? Or should I transfer the ez directory content in the root once i finished my work ? I would like your advice on how best to do this. Thanks, Benj
Łukasz Serwatka	Sunday 19 March 2006 11:27:59 pm Benj, you can of course install eZ publish in www/ez_publish and keep there your development version. When you will done, you can use mod_rewrite rule (without moving files) or move your all files to root directory (www) or setup Virtual Host which will points to www/ez_publish. All possibilities will work. For eZ publish we recommend Virtual Host setup. Check documentation for more information: http://ez.no/doc/ez_publish/technical_manual/3_6/installation/virtual_host_setup Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Bertrand Dunogier	Tuesday 21 March 2006 8:07:16 am I'm gonna add to What Lukasz said that swiching from a developement setup to a production one is pretty easy... I'd recommend that you develop on subdomains (dev.yoursite.com, admin.dev.yoursite.com), then just switch the virtualhost setup / host matching in site.ini when you're done.Everything should work perfectly. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier

Author

Message

Sunday 19 March 2006 3:44:11 pm

Hi,
I finally decided to use Ez publish as it seems to be the ONLY cms to fits almost all my needs right out of the box.

I currently have my site installed in /www/ . This is the web root. So when people go to www.mysite.com they see the index in there. This is where I want the eZ publish index.

BUT.... it will take lots of time for me to setup the site, and convert all my content to ez publish and I don't want people to see my eZ index until I finished the work.

So what is the best solution ? Should I install eZ publish in its own directory ? Is there an option to move the index in the root directory once i'm ready ? Or should I transfer the ez directory content in the root once i finished my work ?

I would like your advice on how best to do this.

Thanks,
Benj

Łukasz Serwatka

Sunday 19 March 2006 11:27:59 pm

Benj, you can of course install eZ publish in www/ez_publish and keep there your development version. When you will done, you can use mod_rewrite rule (without moving files) or move your all files to root directory (www) or setup Virtual Host which will points to www/ez_publish. All possibilities will work. For eZ publish we recommend Virtual Host setup. Check documentation for more information:
http://ez.no/doc/ez_publish/technical_manual/3_6/installation/virtual_host_setup

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Bertrand Dunogier

Tuesday 21 March 2006 8:07:16 am

I'm gonna add to What Lukasz said that swiching from a developement setup to a production one is pretty easy...

I'd recommend that you develop on subdomains (dev.yoursite.com, admin.dev.yoursite.com), then just switch the virtualhost setup / host matching in site.ini when you're done.Everything should work perfectly.

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

eZ debug

Timing:	Jan 18 2025 22:36:15
Script start
Timing:	Jan 18 2025 22:36:15
Module start 'layout'
Timing:	Jan 18 2025 22:36:15
Module start 'content'
Timing:	Jan 18 2025 22:36:15
Module end 'content'
Timing:	Jan 18 2025 22:36:15
Script end

Main resources:

Total runtime	0.0346 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0058	587.9141	152.6250
Module start 'layout'	0.0058	0.0047	740.5391	39.4453
Module start 'content'	0.0105	0.0213	779.9844	89.3359
Module end 'content'	0.0318	0.0027	869.3203	34.3047
Script end	0.0346		903.6250

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	8.8908	14	0.0002
Check MTime	0.0015	4.2946	14	0.0001
Mysql Total
Database connection	0.0008	2.4520	1	0.0008
Mysqli_queries	0.0040	11.5501	3	0.0013
Looping result	0.0000	0.0461	1	0.0000
Template Total	0.0017	4.9	1	0.0017
Template load	0.0009	2.7385	1	0.0009
Template processing	0.0008	2.1979	1	0.0008
Override
Cache load	0.0007	1.9060	1	0.0007
General
dbfile	0.0003	0.9371	8	0.0000
String conversion	0.0000	0.0255	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