|
Author
|
Message
|
|
Jérôme Vieilledent
|
Sunday 27 June 2010 6:14:37 am
Hi everyone ! As a continuation of my presentation at the eZ Conference 2010 in Berlin, here's a topic where we would talk about the subject. Feel free to post any question/notice/suggestion ! My slides on Slideshare : http://slidesha.re/cM6Yk2
|
|
Peter Rudolfsen
|
Sunday 27 June 2010 10:48:30 am
Thanks for a nice presentation, really enjoyed it. I just have one question, do you run the virtual development servers on a dedicated machine, or are they running on each of the developers machines?
|
|
Jérôme Vieilledent
|
Sunday 27 June 2010 2:00:55 pm
You're welcome ! I'm glad you enjoyed it :) About your question, it mainly depends if the developers are located in the same LAN as the database server. If this is the case, then they can run their VM on their local machine. Otherwise (e.g. working with freelancers, home office...), you'll need a dedicated headless server (meaning with no GUI like regular Virtual Box or VMWare player) hosting the VMs. You can do that with Virtual Box thanks to VBoxHeadless (look "headless" in the manual), or with VMWare ESX.
|
|
Peter Rudolfsen
|
Monday 28 June 2010 1:23:29 am
I'm also looking for a best-practice on how to structure the var-dirs. We now have all of the var-dir centralized, but that can cause problems with the cache when on different environments. (INI- and template-cache, etc). site.ini says that CacheDir can be set to an absolute path, and then it supposedly won't be appended after the var-dir. Are you familiar with this challenge?
|
|
Jérôme Vieilledent
|
Monday 28 June 2010 4:21:36 am
I'm not sure I understand your issue... How can a centralized var dir be a problem ? Can you please precise a bit ?
|
|
Peter Rudolfsen
|
Monday 28 June 2010 11:42:00 pm
The problem was sharing the cache-part of the var-dir between environments. Then you could suddenly get cache from integration or other developers when developing. But it seems that setting the CacheDir to a local absolute path did the trick.
|
|
Jérôme Vieilledent
|
Tuesday 29 June 2010 4:52:55 am
Actually, is your issue for production or just for development/integration ?
|
|
Peter Rudolfsen
|
Tuesday 29 June 2010 5:25:16 am
Sorry, I should've specified which environments I was talking about. This issue is only between development and integration, and NOT in production.
|
|
Jérôme Vieilledent
|
Wednesday 30 June 2010 6:04:29 am
Are you in cluster mode ? Do you use the same database for dev/integration ? If so, just consider using 2 separated databases ;)
|
