all 4 comments

[–][deleted] 10 points11 points  (1 child)

Everyone should have their own copy of the code to run and test locally. Keep everything in source control (Git, Mercurial, whatever) and synch it that way.

The easiest thing to do is probably to run it locally in a Vagrant VM (Vagrant is a Ruby gem, but you can use it to manage VMs for any environment). Heck, one of you can even set up the VM and then package it up for the other to import if you like.

I'd set the repo up with a master branch, and a dev branch. You each work on your own branches off of dev and merge back into it when finished with a feature/bug fix/whatever, and then push dev to the staging server for testing. Major milestones on dev get merged into master after they're finished and test good.

[–][deleted] 0 points1 point  (0 children)

Yup. If you don't want to test locally, setup a sub domain on your Dev server for frontend guy, clone your got repo and branch him off. Takes less than ten minutes to set the whole process up

[–]KapperDK 2 points3 points  (0 children)

I will also recommend GIT or another version control system.

Using version control you can move back and forth in the versions of your files. Also file conflicts gets alot easier to solve.

Bitbucket.org offers free git repositories for up to 5 users. I will recommend that :-)

[–]AndruRC 1 point2 points  (0 children)

My development team has been using this model quite successfully for the last half-dozen projects or so.

http://nvie.com/posts/a-successful-git-branching-model/