Sheesh kebab! We are reaping a whirlwind of pain for not having a proper dev environment setup for FOWA.
Here’s the problem: when we launched the site, it was just Gill (my wife and co-Director of Carson Systems) and I FTP’ing files up to the site and using PayPal to allow people to buy tickets.
The new site has a mini web app (“The Lounge” – which allows attendees to network), a proper e-commerce system and a lot more pages than the original. It was designed by Apples to Oranges and built by Dave Stone. It’s hosted on a Rackspace server with Plesk installed.
Here’s the problem – we didn’t setup a proper Subversion repository and deployment script. Updates are a total nightmare now as there are three different parties working on the site.
Here’s what we should have done (duh!):
- Setup a Subversion repository
- Make sure everyone on the team has their own username/pass to the repository
- Get everyone setup with a subversion client
- Create a development and live environment
- Have a one-click deployment setup for pushing code from dev to live
The problem is that it’s a pain in the ass to get these things setup, so most people (including us) don’t do it for every site they have. It’s tempting to just get the site live and start working on it. “We’ll deal with it later!” I said.
Now I know – it’s absolutely necessary (and we’re currently getting this set up for FOWA, Vitamin and our other websites).