You could reduce your need for Internet connectivity by including a small computer that runs the server software
you support -- that may mean two machines if you build for both Windows IIS and Apache on Linux
unless you are quite good at cross-platform development. Then you only need a connection when you have a build to release either direct to operational or to a test environment
depending on your customer.
If you use a good development environment
you can also post only differences, greatly reducing the amount of stuff you have to move. That's easier on Linux
If you have shell access it doesn't take much bandwidth to maintain an SSH connection for loading tarballs previously loaded. You could start a transfer when you go to bed
and do the install when you get up.
It's important to really understand the connection management software on your computer. I use IBM Access Connections because that is what came with my Lenovo laptop
I use for development - you want to be able to manage what happens if you temporarily lose a WiFi connection so the link will re-establish and your transfer pick up where it left off. Similar capabilities work for 3G cellular connections. I can only speak to AT&T, my provider of choice since the quad-band hardware
works pretty much everywhere. Verizon has better coverage in the US but their technology isn't supported much except in the US, China
, and North Korea
. Some high tourist areas have CDMA towers to support US tourists with Verizon in the Bahamas
of the Caribbean