Development workflow, functional testing, etc.

Next topic

Author	Message
Erlend Halvorsen	Tuesday 25 March 2008 4:55:10 am I'd love to hear how other developers work with ez publish. I have several clients on this platform now, and we are constantly adding and removing features, changing templates, modules, etc. For code this is not really a problem, as I keep that in subversion. What is more of a problem is when I need to add or make changes to content classes, add or remove permissions, etc. Everything is so tightly coupled to the production database. On other projects I have worked on, we some times pulled the production data into development, then pushed everything back out again at deployment. However, as soon as you start to use forums, order forms, etc, this is no longer a viable option, as production data is changing constantly. How do you deal with this? Could we maybe get a thread running with some "best practices"? -Erlend
Maxime Thomas	Thursday 03 April 2008 11:04:20 pm Hi Erlend, A kind of thread already exists on eZPublish. It's called ezpedia.org. :-D http://www.ezpedia.org You may find there tips and tricks and I guess lots of best practices. 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
Geoff Bentley	Saturday 11 October 2008 3:27:20 am Here's some links, and it's definitely worth continuing this thread. eZ Systems may have a clever way to do this, but I've not heard anything that has resolved maintaining database configuration across multiple environments. http://www.cjohansen.no/ez_publish/praktisk_ez_publish http://suffandnonsense.blogspot.com/2008/10/how-to-you-handle-revision-control-in.html

Author

Message

Tuesday 25 March 2008 4:55:10 am

I'd love to hear how other developers work with ez publish. I have several clients on this platform now, and we are constantly adding and removing features, changing templates, modules, etc. For code this is not really a problem, as I keep that in subversion. What is more of a problem is when I need to add or make changes to content classes, add or remove permissions, etc. Everything is so tightly coupled to the production database. On other projects I have worked on, we some times pulled the production data into development, then pushed everything back out again at deployment. However, as soon as you start to use forums, order forms, etc, this is no longer a viable option, as production data is changing constantly. How do you deal with this? Could we maybe get a thread running with some "best practices"?

-Erlend

Maxime Thomas

Thursday 03 April 2008 11:04:20 pm

Hi Erlend,

A kind of thread already exists on eZPublish. It's called ezpedia.org. :-D
http://www.ezpedia.org

You may find there tips and tricks and I guess lots of best practices.

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

Geoff Bentley

Saturday 11 October 2008 3:27:20 am

Here's some links, and it's definitely worth continuing this thread. eZ Systems may have a clever way to do this, but I've not heard anything that has resolved maintaining database configuration across multiple environments.

http://www.cjohansen.no/ez_publish/praktisk_ez_publish
http://suffandnonsense.blogspot.com/2008/10/how-to-you-handle-revision-control-in.html

eZ debug

Timing:	Jan 18 2025 11:24:01
Script start
Timing:	Jan 18 2025 11:24:01
Module start 'layout'
Timing:	Jan 18 2025 11:24:01
Module start 'content'
Timing:	Jan 18 2025 11:24:01
Module end 'content'
Timing:	Jan 18 2025 11:24:01
Script end

Main resources:

Total runtime	0.0156 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.0054	589.1641	152.6406
Module start 'layout'	0.0054	0.0032	741.8047	39.4766
Module start 'content'	0.0086	0.0050	781.2813	89.3672
Module end 'content'	0.0136	0.0019	870.6484	34.3047
Script end	0.0156		904.9531

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	16.1181	14	0.0002
Check MTime	0.0012	7.5771	14	0.0001
Mysql Total
Database connection	0.0011	7.0201	1	0.0011
Mysqli_queries	0.0032	20.2356	3	0.0011
Looping result	0.0000	0.1989	1	0.0000
Template Total	0.0014	9.0	1	0.0014
Template load	0.0008	5.0187	1	0.0008
Template processing	0.0006	3.9737	1	0.0006
Override
Cache load	0.0005	3.4397	1	0.0005
General
dbfile	0.0002	1.4291	8	0.0000
String conversion	0.0000	0.0383	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