Very cool. Agree Jason, we should blog about these experiences. So
surprised there is not more online about this. Anytime I find anything
it is so Java-centric. I think it's so important for the PHP community
to have our own perspective and identity. I don't want us to follow all
of Java's techniques and setups, because the two languages are really
two different animals.
On 8/6/2010 3:02 PM, Jason Austin wrote:
Keeping everyone on the same system is WAY easier. VM's are a great
way to make that happen, so I would definitely say try it out. Our
team is relatively small (1 manager, 2 developers, 2 part-time
developers) so we just keep everyone on Apple hardware and don't have
a problem.
Given that there is not a lot of info on this, I'd suggest blogging
your experience once you decide what to do. It may help somebody else
out in the future. Heck, maybe I should do that too :)
- Jason
On Fri, Aug 6, 2010 at 2:54 PM, Paul <z...@zooluserver.com
<mailto:z...@zooluserver.com>> wrote:
Agree Jason. We in fact already do that at my shop. Not
everything is an svn repository though, so that becomes an issue.
We are using PHING to build are web apps and deploy to stagin and
production. So we might add targets for update dependencies,
which would make sure things outside of svn can be
imported/removed/etc.
Where it gets a headache for me is when it comes to the server
itself or operating system, which is why I am leaning towards each
developer having a vm, so we can all run the same os, version,
etc. Then when we need to install an extension, the same steps
should work for the whole team, we could even write scripts to
automate, and put that in the phing target.
Just want to see what the community does, before I start over
thinking this.
On 8/6/2010 2:24 PM, Jason Austin wrote:
svn:externals saved our butts on a lot of that. We setup ZF as
externals in our projects so every time a new instance of the
project is checked out, the ZF library is local to the product in
the htdocs folder. I realize lots of people like using a central
ZF library, but keeping them as externals is the best way to keep
your application dependencies on ZF (and any other library) in
your repo. We also support about 30 applications, so its not
feasible for all of those to use the same ZF library or all we
would ever do is update applications to use a new version of the
framework.
- Jason
On Fri, Aug 6, 2010 at 2:14 PM, Paul <z...@zooluserver.com
<mailto:z...@zooluserver.com>> wrote:
Well Tortoise Subversion is just a svn client. I have that
all sorted. The issue is where are the local copies stored.
Centralized dev server or each developer local machine.
Wanted to see most organizations do, and some best practices.
On 8/6/2010 1:51 PM, Deborah Dalcin wrote:
Should also check out tortoise subversion. It's not without
it's problems, but it's a pretty solid tool.
On Fri, Aug 6, 2010 at 12:18 PM, Paul <z...@zooluserver.com
<mailto:z...@zooluserver.com>> wrote:
We currently use PHING, I have heard of Apache Maven,
will look into this.
On 8/6/2010 12:00 PM, Hector Virgen wrote:
Apache Maven
--
www.pseudoworlds.gibbserv.net/mms
<http://www.pseudoworlds.gibbserv.net/mms>
www.killk.gibbserv.net <http://www.killk.gibbserv.net>
--
Jason Austin
Senior Solutions Implementation Engineer
NCSU - OIT - Outreach Technology
jason_aus...@ncsu.edu <mailto:jason_aus...@ncsu.edu>
--
Jason Austin
Senior Solutions Implementation Engineer
NCSU - OIT - Outreach Technology
jason_aus...@ncsu.edu <mailto:jason_aus...@ncsu.edu>
