Morning folks, Further to this discussion re: Version control, Testing/Staging/Production environments.
Does anyone have any tips on handling design and asset management for a web development project in subversion? I mean PSD's, logos, html prototypes. I assume they would be kept in a seperate repo (if version controlled at all) from the site base code. I'm just trying to get my head around how a design team fits into this, and if they even need to at all. Regards Aaron Cooper ----- Original Message ----- From: Aaron Cooper To: [email protected] Sent: Wednesday, July 22, 2009 10:06 AM Subject: [phpug] Environment setup, source control and Deployment procedures I know this topic depends alot on the organization, but I am looking into Development/Staging/Production enviroments, how they interact with source control (SVN) and Deployment procedures from Staging to Production in a bid to build a case study for my employer. While I totally understand the environment side of things, just how source control fits in to each environment, and deployment procedures are a bit grey for me. I'm also a bit grey on how each environment should be setup in terms of hardware. Obviously Production should be on it's own, but is having Development and Staging on one box a terrible idea? What I am looking for is examples of systems from Development to Production. I was wondering if you lot know of some good literature or online resources on this topic (with examples). PHP specific examples aren't nessecary, but a Web Development focus would be handy obviously. Cheers Aaron --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
