Cross-Site Multi-Platform Development Concerns

I'm currently developing a web-based application on multiple machines and
multiple networks. I have multiple computers on my home network which I'm
using for development, as well as multiple computers at work. I'm using CVS
for revision control.

Up until now I've been doing the development on each machine and keeping the
code in sync with CVS. This has worked fine, but now I'm running into some
hurdles. Now that much of the backend is complete and I'm ready to start
developing/testing the web-based front-end, I am stuck.

I'd really like to have one central development web server to handle my
testing. The problem is, everytime I want to push changes onto the server,
I have to do a cvs commit, and then a cvs update on the server side. To me,
there's just something inherently wrong with rev'ing your source everytime
you want to push it onto the server, especially for small, incremental
changes--but perhaps this is a normal way to handle this, and I should just
get over it.

So, the second option I've considered is actually installing a testing
platform on every development machine. This means installing Apache, mysql,
and any other supporting infrastructure for my app on every machine. I knew
this was a bad idea from the beginning, but went forward with it anyway.
Problems include platform-specific coding requirements (i.e.
#!c:\perl\bin\perl.exe in windows vs. #!/usr/bin/perl in unix at the top of
the code), issues keeping the mysql db in sync, etc.

Can anyone advise me on how to proceed? I guess my best option right now is
to manage the whole process with CVS and have one central testing server.
I've considered other options, such as the built in ftp/ssh functionality of
vim, to modify code remotely in a local vim session, but this is slow and
tedious. I'm not a big fan of developing inside of a ssh/telnet session for
the same reasons.

I guess ideally I'd like to be able to develop my code locally under any
platform, and then push a button and have the changes propogate to the
testing server. Perhaps something like cvs that doesn't require two steps,
i.e. commiting on the local side and updating on the server side, and also
doesn't require rev'ing the hell out of your code just so you can validate
changes.

Does anyone have any creative ideas or advice on how to handle this?
.