Our web development shop is divided into two groups, at the moment: LAMP developers and Windows developers. The LAMP folk are currently using Bazaar for version control, and doing development on a remote development server. Both the shared repositories and the individual checkouts are on said server, so checkouts usually look something like:
bzr checkout /bzr/someproject/trunk ~/public_projects/someproject
Most of us edit files over SFTP, and do our commits, updates, etc., to version control via SSH and the command line.
There's a push, though, for some of the current Windows folk to get into LAMP work, and we're in the process of evaluating tools to help ease the transition for the people not so comfortable with the command line. They all use IDEs with integrated version control, and we'd like to offer something similar.
It seems, though, like the only way we can get the IDEs to play nice with our remote working copies is to do some sort of SFTP mount, and do a remote checkout, like:
bzr checkout bzr+ssh://user@host/bzr/someproject/trunk /path/to/sftp_mount/someproject
Which means every single update or commit requires repository data to be downloaded locally, parsed by the local DVCS executable, and uploaded to the server, again, which seems wasteful and stupid. Even IDEs that have extensions both to do remote files and DVCSs don't seem to let you do both together (we've played with Eclipse RSE and BzrEclipse, for example). We're not tied to any particular DVCS or IDE at this point, but would like to find some combination of tools that handles our workflow in a sane way (that is, can use the DVCS binaries on the server and skip the back-and-forth). Thoughts?