Hi,
Thanks for all answers. Please let me add that I do use CVS (migrating to
SVN) and the reason to use samba is that doing this allows the developer
machine (windows) to access the shares hosted in a linux server so when
he/she tests it will be run in the 'same' environment that the staging
Hi,
Thanks for all answers. Please let me add that I do use CVS (migrating
to
SVN) and the reason to use samba is that doing this allows the developer
machine (windows) to access the shares hosted in a linux server so when
he/she tests it will be run in the 'same' environment that the
Thanks for all answers. Please let me add that I do use CVS (migrating to
SVN) and the reason to use samba is that doing this allows the developer
machine (windows) to access the shares hosted in a linux server so when
he/she tests it will be run in the 'same' environment that the staging and
On May 19, 2008, at 8:45 AM, Zoltán Németh wrote:
Hi,
Thanks for all answers. Please let me add that I do use CVS
(migrating
to
SVN) and the reason to use samba is that doing this allows the
developer
machine (windows) to access the shares hosted in a linux server so
when
he/she tests
Or depending on your budget, Switch the developers to Macintosh
computers, install windows via parallels, and then you can test in
Mac/Unix/Windows all from 1 computer :)
And watch everyone quit... :-)
--
Richard Heyes
++
| Access SSH with a Windows
Hi Zoltan,
If the windows would be used just for IE I think it's cheaper to have one
windows machine (server 2003/2008), have the users connect via terminal
service (rdesktop). I think it's easier than having to install/maintain
than multiple windows installations, even if it is a virtual
Unfortunately this is not an option due to budget :) I use Mac myself (with
VMWare fusion) but would not be feasible to depoly this with all the devel
team.
Or depending on your budget, Switch the developers to Macintosh computers,
install windows via parallels, and then you can test in
On May 19, 2008, at 520AM, robert mena wrote:
So, in order to allow phpunit to be ran, have the firefox/IE support
and use
xdebug I have two basic options:
a) stay with windows, install XAMPP (or any other all-in-one). And
live
with the fact that some things will have to be taken care of
Hi Zoltan,
If the windows would be used just for IE I think it's cheaper to have one
windows machine (server 2003/2008), have the users connect via terminal
service (rdesktop). I think it's easier than having to install/maintain
than multiple windows installations, even if it is a virtual
Hi,
I am looking for tips regarding improving the development process. I'll
explain my current setup and please feel free to comment.
My developers all use windows + eclipse PDT, the workspace is hosted (via
samba) in a Linux server with Apache/PHP/MySQL. I am in the process of
adopting Unit
2008/5/10 robert mena [EMAIL PROTECTED]:
I am looking for tips regarding improving the development process. I'll
explain my current setup and please feel free to comment.
My developers all use windows + eclipse PDT, the workspace is hosted (via
samba) in a Linux server with
I suggest you if you are running live on linux, then developing on
linux, could be the same dist or not..
but definitely don't mix OS, because the extensions could fail, etc.
one big issue it's the case insensitive in windows.
definitely some version control system such as SVN or GIT
you can use
12 matches
Mail list logo
