|Need Suggestion: Eclipse PDT/Zend Studio in Team Environtment [message #751186]
||Tue, 25 October 2011 22:01
| Viktor Iwan
Registered: October 2011
at the moment, me and other 4 coworker is using dreamweaver with one local server using dreamweaver's build in check in/out
Now since we move to PDT, we found problem on having this kind of team environment workflow, and i want to ask suggestion for the forum here about the best practice for collaboration work ?
should we use 1 local server ?
or each workstation should install with a local server ?
Your suggestion is highly appreciate
|Re: Need Suggestion: Eclipse PDT/Zend Studio in Team Environtment [message #752392 is a reply to message #751186]
||Wed, 26 October 2011 07:27
Registered: July 2009
On 2011-10-26 04:01, Viktor Iwan wrote:|
> at the moment, me and other 4 coworker is using dreamweaver with one local
> server using dreamweaver's build in check in/out
> Now since we move to PDT, we found problem on having this kind of team
> environment workflow, and i want to ask suggestion for the forum here about the
> best practice for collaboration work ?
This depends on what You want & need, what is Your network schema?
> should we use 1 local server ?
This is ok when:
+ You need more services on that server (ssh, svn, database etc.)
+ You need different OS or specific OS other than development team have
+ someone will take responsibility for this server
+ All servers changes are applied only for one machine
The major disadvantage is that when this server is down then team is unable to
> or each workstation should install with a local server ?
This is ok when:
+ You sometime want to work outside office (with slow or without network)
+ every team member know how to setup and manage all needed services
+ there are no changes in configuration etc.
+ you don't need additional server to work on project
+ projects are simple so they can work on both win and linux
The worst thing about this scheme is that there are always difference between
computers and You will lose big amount of time on this. I don't recommend that
for anyone, You can always have second apache locally in case of something but
You will notice that it's just better to do everything once.
> Your suggestion is highly appreciate
For first scheme setup samba connection, map drive and set up sync builder as
first for project, it's working perfectly.
For second You can just create symlink or set www server document root dir as
As I said - first aproach is much better but more complex, require additional
hardware and some services, but I will never come back to second one.
Powered by FUDForum
. Page generated in 0.01762 seconds