I have an SVN server installed on my machine. But since I am using a router to connect to internet, people are unable to ping/connect me. That means they cannot access my SVN server using the IP from whatismyip.com website.
Is there a way by which people connect to some utility (e.g. teamviewer) which would be installed on my machine and that utility intern talk to SVN server I already have?
If the above is not possible, is that any solution to the problem (connect to version control server without knowing the IP of the server but by some other means).
Thanks for the reply. I understand its not obvious. What I thought one way of doing it is:
I have a machine where SVN server is installed. This machine is using a proxy. That means outside world cannot directly access the SVN server, right?
Now there is some service provide. I register my machine to that provider which means that service provide knows me when I am online and can send and receive data to some utility (something like gtalk) which intern sends talk to my SVN server.
Now the user with SVN client(say eclipse) would talk to that service provider which would forward the data to my svn client.
Something like this is possible? Or some other solution is possible?
Actually I am working on a small project thus don't want to spend on buying static IP or some space for SVN. If the above does not work, can you suggest some good sites which provide free hosting of personal (not open source) project with 2 or more client access?
author & internet detective
Most routers provide a mechanism to provide open ports so that outsiders can connect to ports on your machine. You will have to read the router's documentation, or google for some tutorials, to figure out how to do that. Once the port is open, then others will be able to access you SVN repository.
Not that with the port open your machine will then be subject to port scans, DDOS attacks, and other bad things which you currently do not notice because your router quietly blocks them.
By the way, good luck with this. Router documentation varies from useless to incomprehensible, at least from what I have seen. The googled tutorials might be a better bet.