how to separate admin,site interface

«

Previous topic

|

Install & configuration

|

Next topic

»

Author	Message
kutty pappa	Wednesday 11 March 2009 1:32:09 am hi, I’m new to ezpublish, just started learning. Could any one tell me how to separate admin interface from site interface. Idea is have two different servers, one for admin interface and another one for site interface. Thanks in advance,
Andreas Kaiser	Wednesday 11 March 2009 4:42:20 am This is possible having 2 ez publish installations that share the same database: Server A ezpublish install with "public" siteaccess configured with DB1 (could be hosted in Server A or B, or even in a dedicated server) Server B ezpublich with "admin" siteaccess configured with DB1 Important is that both siteaccess use the same db to have consist content in both areas/sites. By the way, not sure why you want to have 2 server, because of security? because of performance? We have a client that wants 2 server (a production and test server) because of security concerns, but in this case the environment are completely separate and using different db, and because of this content is not "updated" in real time in production server. Last, you also can check if a one server, or ezpublish cluster environment would work for you... eZ Partner in Madrid (Spain) Web: http://www.atela.net/
Ivo Lukac	Wednesday 11 March 2009 7:52:02 am To have one db is easy, problem is file storage. You have 2 solutions: - use cluster file handler (which stores file in db) - or place storage dir on some shared space (NAS or SAN) http://www.linkedin.com/in/ivolukac http://www.netgen.hr/eng/blog http://twitter.com/ilukac
kutty pappa	Wednesday 11 March 2009 11:17:49 pm Thanks you very much for quick response. We thought of separating it, because of security reason. Want to keep admin interface in intra server.
Andreas Kaiser	Thursday 12 March 2009 10:51:34 am Hi, By the way, we will setup similar concept (development server in client and production server(s) public available) in the next weeks/month. But in our case separate db because of security (admin users and siteaccess will only be in development server) and 2 public servers - because of location (one in USA and 2nd in Europe). I can send you more in deep information about this setup if you want (like directories to copy, database tables to copy, etc). eZ Partner in Madrid (Spain) Web: http://www.atela.net/
kutty pappa	Thursday 12 March 2009 11:10:28 pm Hi Andreas Kaiser, Thank you very much for immediate response. Quite interesting, please give me more information. If you give me step by step setup manual will help me more. Let me try it out.

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 30 2025 21:40:52
Script start
Timing:	Jan 30 2025 21:40:52
Module start 'layout'
Timing:	Jan 30 2025 21:40:52
Module start 'content'
Timing:	Jan 30 2025 21:40:52
Module end 'content'
Timing:	Jan 30 2025 21:40:52
Script end

Main resources:

Total runtime	0.0214 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0050	588.2578	151.2266
Module start 'layout'	0.0050	0.0034	739.4844	220.7188
Module start 'content'	0.0084	0.0116	960.2031	1,001.8359
Module end 'content'	0.0200	0.0014	1,962.0391	37.9922
Script end	0.0214		2,000.0313

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	12.3230	14	0.0002
Check MTime	0.0010	4.7953	14	0.0001
Mysql Total
Database connection	0.0006	2.9993	1	0.0006
Mysqli_queries	0.0020	9.1102	3	0.0007
Looping result	0.0000	0.0512	1	0.0000
Template Total	0.0009	4.3	1	0.0009
Template load	0.0007	3.3073	1	0.0007
Template processing	0.0002	1.0031	1	0.0002
Override
Cache load	0.0005	2.3643	1	0.0005
General
dbfile	0.0003	1.2678	8	0.0000
String conversion	0.0000	0.0311	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