Subversion (svn) server: developers
102 views
Skip to first unread message
Dan Grayson
Jul 11, 2010, 11:48:26 AM7/11/10
to Macaulay2
We are going to move our subversion server to a different location on
the internet some time during the next week or so, as the physical
machine that hosts it is getting old. There may be an interruption in
service, but we'll try to make it as brief as possible.
If there is an interruption, those doing active development can make
backups for themselves by using "svn diff >mybackupfile" to create a
file, and saving the file somewhere safe.
The new domain name will be "svn.macaulay2.com", but it is not yet
pointing to its final location on the web. The "svn switch --
relocate" command will be what users of the repository will need to do
to switch over to the new location, when I announce that it's ready.
When I know more details I'll announce them here.
the internet some time during the next week or so, as the physical
machine that hosts it is getting old. There may be an interruption in
service, but we'll try to make it as brief as possible.
If there is an interruption, those doing active development can make
backups for themselves by using "svn diff >mybackupfile" to create a
file, and saving the file somewhere safe.
The new domain name will be "svn.macaulay2.com", but it is not yet
pointing to its final location on the web. The "svn switch --
relocate" command will be what users of the repository will need to do
to switch over to the new location, when I announce that it's ready.
When I know more details I'll announce them here.
Dan Grayson
Jul 11, 2010, 4:57:38 PM7/11/10
to Macaulay2
Okay, the new subversion server is up and running at
svn.macaulay2.com, serving up the repositories in a read-only way.
Eventually I'll restart the old server read-only, copy the files over
again, and then restart the new server in read-write mode.
If you want to experiment before we go live and give me some feedback,
try it out using the instructions below.
Here is the svn command to switch over to the new location; users
should type it in the top level of their checked out source tree:
svn switch --relocate svn://macaulay2.math.uiuc.edu svn://svn.macaulay2.com
Then check the result with
svn info
The error message displayed when trying to modify a read-only
repository is "Authorization failed".
Undo the switch with
svn switch --relocate svn://svn.macaulay2.com svn://macaulay2.math.uiuc.edu
Users with svn accounts will have to enter their subversion password
once again.
The new server machine is a virtual machine rented from slicehost.com,
running the latest ubuntu distribution of GNU/linux.
svn.macaulay2.com, serving up the repositories in a read-only way.
Eventually I'll restart the old server read-only, copy the files over
again, and then restart the new server in read-write mode.
If you want to experiment before we go live and give me some feedback,
try it out using the instructions below.
Here is the svn command to switch over to the new location; users
should type it in the top level of their checked out source tree:
svn switch --relocate svn://macaulay2.math.uiuc.edu svn://svn.macaulay2.com
Then check the result with
svn info
The error message displayed when trying to modify a read-only
repository is "Authorization failed".
Undo the switch with
svn switch --relocate svn://svn.macaulay2.com svn://macaulay2.math.uiuc.edu
Users with svn accounts will have to enter their subversion password
once again.
The new server machine is a virtual machine rented from slicehost.com,
running the latest ubuntu distribution of GNU/linux.
Dan Grayson
Jul 14, 2010, 9:51:13 PM7/14/10
to Macaulay2
Things seem to be running well on the new server, so I think we'll
switch over some time tomorrow. After the switch, I'll advertise it
here and send a message to the mailing list.
switch over some time tomorrow. After the switch, I'll advertise it
here and send a message to the mailing list.
Dan Grayson
Jul 15, 2010, 12:36:00 PM7/15/10
to Macaulay2
Our new subversion source code server at svn.macaulay2.com is now
live, and the old one is running read-only. If you get an
authorization error when trying to check in a file, that means it's
time to switch over to the new one. Here is the command, which should
be issued at the top directory of the directory tree checked out from
the server:
Backups are done on the server in multiple ways, but keep your work,
too.
live, and the old one is running read-only. If you get an
authorization error when trying to check in a file, that means it's
time to switch over to the new one. Here is the command, which should
be issued at the top directory of the directory tree checked out from
the server:
Backups are done on the server in multiple ways, but keep your work,
too.
Reply all
Reply to author
Forward
0 new messages