Subversion Deployment and Testing

Question

I have a client that I am trying to convince in the implementation of Subversion (I know, I know). My step sounds something like this: his test domain is visible to Google and other web browsers, despite all his efforts (robot.txt does not stand up). By placing the repository at the svn: // URL, we could avoid scanning the code before deploying it in the real domain.

My question is: is there a way to deploy to a test domain and then return it after the job is done. I assume that what I am asking for is a means of switching the test domain easily and simply, as well as through Subversion or some kind of tool in combination with Subversion.

This is more of a customer management problem, but you still haven't let me down.

Answer 1

There are many reasons to use SVN, but I don’t think that “preventing your code from being scanned” is one of them.

If your development areas and code can be crawled by search engines, you are facing a serious system administration problem. There are dozens of solutions to this problem ... IP white lists, HTTP authentication for each site, ACLs for each domain, etc. HTTP Auth takes 5 seconds to configure ... you really need to do something.

SVN , . Google " SVN" .

, , SVN. , -, , , . , , .

Answer 2

, - svn - .

Google , ? localhost ?

Answer 3

URL-/ .htaccess . Subversion.