name mode size
about 040000
cgi-bin 040000
css 040000
docs 040000
donate 040000
download 040000
eff 040000
en 040000
getinvolved 040000
images 040000
include 040000
js 040000
manpages 040000
press 040000
projects 040000
torbutton 040000
tordnsel 040000
.gitignore 100644 2.57kB
.htaccess 100644 1.83kB
Makefile 100644 1.34kB
Makefile.common 100644 13.92kB
Makefile.local.sample 100644 398B
README 100644 2.22kB
favicon.ico 100644 1.15kB 100755 19.87kB
publish 100755 1.11kB
robots.txt 100644 23B 100755 6.37kB 100755 8.72kB
Here are the instructions I sent David Fifield when he asked about editing the website. I hope they are useful for you too! --Roger See the Makefile.local file in your website/trunk/ directory. Uncomment TORGIT and point it to a tor git. Then apt-get install wml and (alas) probably a shocking number of other debs. Then you can type 'make' and it will build the website for you locally. It's probably a smart move to see whether 'make' works before you svn commit any changes to the wml file. You can edit docs/en/pluggable-transports.wml (and that is the right source file to edit, not the html). But go take a look at that file. You'll notice it has a bunch of tags like <version-torobfsbundlelinux64alpha>. If you're just bumping version numbers, you probably just want to change the definition of those tags. They're in include/versions.wmi (Every once in a while you may need to edit pluggable-transports.wml too -- generally when you change the file name so drastically that just changing the versions.wmi tags isn't enough.) If you want to push your locally built website to the remote webserver, run the ./publish script in website/trunk/. It will rsync everything over, and then it will ask to run its trigger-mirrors script which causes www-master to rsync to all the servers in the rotation. To push the website, you'll need to be in the torwww ldap group (which is separate from whether you can commit to svn). Alas, isn't in version control. You write to it by ssh'ing to and going to /srv/ and then sticking your stuff there. When you want it to go live, you run ./publish from your local website checkout, which will trigger the trigger-mirrors run. (It's possible that you can simply run /home/mirroradm/bin/trigger-mirrors on www-master too, but I've never tried.) Weasel has hopes that somebody will write some scripts to make maintaining packages in dist/ less awful -- automatically check that they have signatures and that the sigs match, that the items on the website are in fact in dist, only allow certain people to put files in certain places, etc. One day! :)