homemili.blogg.se - Windows smartsvn

#WINDOWS SMARTSVN INSTALL#
#WINDOWS SMARTSVN ZIP#

If everything went ok, you should see the new server name in the Transactions pane, with everything else exactly as it was with the old server. Only change the IP-address or host-name into the new IP-address or host-name, click Relocate and wait a while. To point your working copies to the repositories on the new server, simply open a working copy and choose the following menu-item:

To maintain working copies and repositories, I use SmartSVN, IMHO the best tool out there for SVN.ħ. On my CentOS server, I had to specifically open the port for svnserve in the firewall. $ echo "svnserve -d -r /var/svn" > /etc/rc.local For Linux (CentOS in my case) you can simple add the following statement to the file /etc/rc.local: $ launchctl load /Library/LaunchDaemons/.plist

#WINDOWS SMARTSVN INSTALL#

Then edit the file and change the values, prior to loading it into launchctl.Īnyway, I zipped the plist-file and you can download and install it right away in /Library/LaunchDaemons/ (download: .plist)Īfter you installed it, and you made your changes (for example change /Users into /var), execute the following command to add the script to launchctl:

you want to run svnserve under a different user/group, and/or.

your installation of svn is not in /usr/bin/, and/or.

There are various plist files circulating the internet, so I took one and modified a few settings so you will not have permission problems and do not have to modify it again. For MacOS X we need to make a startup script for it in MacOS X’s application launcher, launchctl. To check if it is already running, execute the following command:ĥ01 20397 20385 0 7:36pm ttys000 0:00.00 grep svnserveĥa. I use the standard svnserve daemon to access my repositories. Do ls -l to check if the owners and permissions are ok.ĥ. The svn directory is now completely restored on the new server. $ mv svn.zip /var/ (or /someotherfolder/) If this shows nothing, install SVN first. If you use VNC, start a Terminal application on the remote server to get a command prompt. If you cannot log in as root, log in as an administrator and you probably have to use ' sudo' before every command you execute to get the right permissions.Ĥa. Now, start either an SSH or VNC session to your new MacOS X or Linux server.Īgain, log in as root. Now send the file to your new server, per FTP or SFTP, whichever you prefer or are able to use:ģ. In my case I zipped the svn directory, because that is where I store all repositories:

#WINDOWS SMARTSVN ZIP#

To get an exact copy onto the new server, zip all repositories at once. At the prompt ($), execute the following commands:įor example, my repositories on MacOS X reside under /Users/svn/, so I do $ cd /users. If you use VNC, start a Terminal application on the remote server to get a command prompt.Ģb. If you cannot log in as root, log in as an administrator and you probably have to use ' sudo' before every command you execute to get the right permissions.Ģa. If you may only access your new server via an SSH-tunnel, just use the SSH-command line. I do not know if these applications support VNC over SSH. For VNC sessions, you can use Chicken of the VNC or Apple Remote Desktop. Start either an SSH or VNC session to your old server.