#32031 closed task (fixed)

Make new svn.tpo static component

Reported by: arma Owned by: anarcat
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #15948 Points:
Reviewer: Sponsor:


Our plan for #15948 involves shutting down the svn service, and rescuing a few of the directories from svn and putting them on a static website component to be served by some of our webservers.

I have collected the files that we should put there:

I believe step one is to make the static component, step two is to populate it and sync it, and then step three is to do a switcheroo with dns so svn.torproject.org points to the new place. Then step four is to shut down the old public svn service at our leisure.

This ticket is mainly for step one. :)

Child Tickets

Change History (8)

comment:1 Changed 13 months ago by weasel

If we put it on a static webserver, then the svn client will not be able to download the contents, and there will not be history etc.

That's fine, but maybe we should not call it svn.torproject.org then? How about svn-archive or svn-attic or something like that?

comment:2 Changed 13 months ago by arma

Part of the goal is to not break the already existing links from places around the internet to svn.torproject.org.

So we could make svn-archive or svn-attic but then I would be also asking you for an svn.tpo and setting up rewriterules on it to get to this archive or attic site.

comment:3 Changed 13 months ago by weasel

I don't think I'd mind the redirects, and I think it makes it clearer that there is in fact no svn service on the target host.

comment:4 Changed 13 months ago by arma

Ok. I could get behind a separate hostname if you feel that we need it. I'd pick "svn-static.tpo" -- because this is not an attic, these are actual files that are still active and useful. For example, the Tor design document (pdf and html) is served from this site.

comment:5 Changed 13 months ago by weasel

I don't have strong preferences. Whichever you prefer really, and if that's svn that's ok too.

comment:6 Changed 13 months ago by anarcat

i like svn-archive, because that's kind of what it is, an archive (even if partial). it's not just a static copy of the SVN repository (in which case it might actually be functional), it's an (incomplete) archive. it could also be modified to have a frontpage or README of some sort that points to the full IA archives as well, or other places where the stuff have been moved to. it should point to #15948 as well, for example.

comment:7 Changed 13 months ago by anarcat

Owner: changed from tpa to anarcat
Status: newassigned

comment:8 Changed 13 months ago by anarcat

Resolution: fixed
Status: assignedclosed

i created the static component, under https://svn-archive.torproject.org

it just lists "forbidden" for now, because there's nothing in there, but i guess that's step two. :)

arma, i'll let you deploy step two if that's alright with you. reopen otherwise.

Note: See TracTickets for help on using tickets.