Is it possible to connect to more different SVN servers using SVN Tortoise Client from one computer?
E.g. (Folder 1 and Folder 2 both on one PC.):
Folder 1 - connected to SVN server X
Folder 2 - connected to SVN server Y
Yes, you can check out working copies from as many SVN servers, repositories or individual paths as you wish. There is no persistent connection to the server with Subversion - the working copy has metadata that instructs the client what repository URL to connect to when it needs to communicate with the repository. But it works in a disconnected mode - unless you're performing an action that requires information from the repository, the client does not communicate with the server.
Related
I am trying to set up an infrastructure where a server folder is mapped into a local directory using SSHFS. This local directory, then, serves as the project folder for Eclipse/Aptana. I would like to be able to work on this project and then push the changes to remote, when needed (from my local machine).
The problem I am having is setting up the SSH keys. Namely, should there be 2 keys (local and server where the original SSHFS source is located) or just one? If there is only one key that was made on the server, will my local machine be able to use it somehow through SSHFS?
Is there a better way to achieve what I am trying to do?
I manage a team of developers who are editing files on a headless development server via SFTP. We use Mercurial (HG) to version the files. It's my job to make sure the team is doing the correct things, so I need to be able to do hg status and hg diff and so forth. Up to now I've been doing this over SSH on the command line, but I would like to be able to use HG Workbench, or something like it, over SSH. Something to send the needed commands over SSH, parse the response, and display the results. I believe this is how Workbench works anyways, but only on the local machine, and I don't see any option to do it remotely.
Is there any workaround way to do this, or another program that can do what I'm trying to do with Workbench?
You have a couple of options:
Clone the mercurial repository to your local machine and then run tortoise hg on your local machine. When you do a push of any modifications they will be synced onto the remote machine - it is a distributed VCS after all.
On the remote machine type hg serve and it will run up a web server. You can then connect to the web server with a browser and perform the operations that you need via the web interface.
What I have ended up doing is using the PHPStorm IDE to do this for me. It is able to sync the working directory with the remote server, including the .hg files, and I can then see the differences in an easy way, as well as do commits right from the IDE.
we have created our repositories on Windows-PC using tortoiseSVN. Now we would like to have on our webserver (Linux-Debian, directory ..../html/, reachable using our domain, user= www-data) a svn-working-copy.
Which steps are to be taken to create a svn-working-directory on our Debian-webserver from our Windows-repository?
Thanks in advance
You need to be running an actual Subversion server (Apache or svnserve), not simply accessing a repository created on a file share via file:///. Once you have that set up, just perform an svn checkout just like you would any other working copy.
I have recently installed Tortoise SVN on Windows and have two computers, A and B. On both machines I installed TortoiseSVN and they are connected Via LAN and I have my repository saved in computer A. I want to access/checkout the repository in Computer A from Computer B, so i tried this URL in the repository to SVNcheckout from Computer B,
http://192.168.2.6/Repository
but i got a error message as,
repository moved permanently to 'http://192.168.2.6/Repository'; please relocate
tried some other URL's as well like,
http://192.168.2.6/C:/wamp/www/Repository/
http://192.168.2.6///C:/wamp/www/Repository/
file:///192.168.2.6///C:/wamp/www/Repository/
but got error messages as,
access to 'http://192.168.2.6/C:/wamp/www/Repository/'; forbidden
What am I missing ?
Got the solution myself, I didnt actually have a SVN server installed, with which i could retrieve the repository through a specific URL from other computer. I installed VisualSvn and that solved the problem..
It is able to do that on LAN.
1. Remember to share the folder you use as repository
2. On pc B, select SVN checkout..., click the browse button, locate to that shared folder.
And it's done.
Here's the situation:
subversion is already installed in the server and I have access to one of the shared accounts in the server (not the root), and this shared hosting account has SSH access.
I want to create a repository where I can commit the PHP files i'm working on, and when I commit it should be viewable in a browser that is why I was thinking of creating the repository folders inside public_html is this a correct way to do this? How about the security of the server? If not what is the correct and proper way to do this?
I would also need help in creating the repository via SSH with Putty. Is there a step-by-step guide online for this?
Server information is as follows:
cat /proc/version - output this:
Linux version 2.6.9-89.0.3.ELsmp (mockbuild#x86-005.build.bos.redhat.com) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-11))
svn --version - output this:
svn, version 1.1.4 (r13838)
compiled Aug 10 2009, 23:17:10
ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
handles 'http' schema
handles 'https' schema
ra_local : Module for accessing a repository on local disk.
handles 'file' schema
ra_svn : Module for accessing a repository using the svn network protocol.
handles 'svn' schema
The correct way to do this is to use a web bridge to SVN, such as websvn or viewsvn (there are several). You can set these up to expose any repository as a website.
As to creating a new repository, see the SVN "Red-Bean" reference at http://svnbook.red-bean.com/
I want to create a repository where I can commit the PHP files i'm working on, and when I commit it should be viewable in a browser.
I'm not sure I understand your question. Do you mean that the repository should execute your PHP, i.e. that your Subversion repository should also be your PHP server? I strongly recommend against it.
A source control repository and an application server are completely different things. They serve different roles; should be accessed by different people (developers vs. end-users); should have different monitoring and SLA policies; different hardware, and whatnot. You also probably don't want every committed change to be automatically deployed to your production environment.
The Red Bean book also has a number of sections on integrating SVN with apache, etc. But before you start working on a solution, you need to define what you're trying to do more thoroughly. What is your usage model?
For example, will you commit to SVN repository via svn+ssh, or via svnserve, etc?
Do you want to see full revisions, history, changesets from the web interface? Or just the head?