Amidst my busy schedule at work, I occasionally find some time to study/code/work on my pet ASP.net projects (most of them exploring new concepts/designs). And I do that @ home too, during weekends/evenings/free time. One major difficulty I found was that I am starting to maintain 2 code bases (one in office, one at home). Am behind a proxy @ work and behind a wireless router at home (the ISP gives me a dynamic IP I believe). And at both places, I have WinXP. Is there a way I can configure any source control (hopefully open source, and may be subversion, as I know to use it). I can access my machine at home from work using TeamViewer, so can find my IP/change settings etc. Is there a way to configure subversion at my home computer so that I can access it from work ?
|
feedback
|
|
Perhaps you are unable to access your home Subversion instance because you have it set up to use the svn:// protocol, which your work router is blocking..? Instead, you could set up your home Subversion server to use https:// protocol. Your work router is more likely to permit https:// traffic (port 443) than svn:// traffic (port 3690). HTTP over port 80 would also work, but I'd prefer SSL for protecting my source code. Here's an article that discusses setting up a Subversion server on Windows with Apache (for http protocol: How to Setup Subversion + Apache + WebSVN on Windows. Here's another article: HOWTO: Subversion for Windows with Apache server - a beginner's guide To solve your dynamic IP issue, use a service like DynDNS.com. | |||||||
feedback
|
|
Phew, I found that google (and MS codeplex) can host your code in SVN. I created a new project in google code and it solves my purpose. AnkhSVN & TortoiseSVN serve my purpose. The only thing is I have to agree to some sort of open source license and this repo is for my personal use, so not too concerned about the license | ||||
|
feedback
|
|
I used google code with SVN, and then later switched to HG. Never had any problems until my employer started blocking https through the proxy. | |||||
feedback
|
|
Perhaps a different approach would be to use an external provider of svn hosting. | |||
|
feedback
|
|
The easiest way is probably to forward your Subversion server to the public internet via the port forwarding of you router. This can usually be configured in the control interface of the router. Also, you'll need the external IP of your router; easiest way would be to use something like DynDNS. Just make sure the server is always well patched. :-) Another possibility would be to use a hosted SVN server somewhere. There are both free and paid options available. | |||||
feedback
|
|
Sorry for off-topic, but are you aware that if your pet project will eventually grow into something useful, your employer can claim ownership of it (because you are using his time and resources)? | |||
feedback
|