Trac:
Cc: weasel to weasel, phobos

To stay comfortable I would set the disk space to 5GB.

The site is only static content.

It will be running some cronjobs that will download from the ooni-probe git repository the documentation and run some scripts to build the documentation.

This cronjob should run once every week.

The content of the cronjob is basically:

git pull && make html

Where the content of the Makefile is:

https://gitweb.torproject.org/ooni-probe.git/blob/HEAD:/docs/Makefile

Trac:
Cc: weasel, phobos to weasel, phobos, aagbsn

We don't compile anything on the webservers. Can you push static html?

Trac:
Cc: weasel, phobos, aagbsn to aagbsn

Replying to phobos:

We don't compile anything on the webservers. Can you push static html?

That makefile does not compile code, it just runs a set of python scripts that automate the creation of the static HTML content.

This is the debian package for it:

http://packages.debian.org/source/squeeze/sphinx

If running cronjob driven python code is a problem I can run the "build" scripts on my local machine and just push static HTML, though I would ideally want this to run on tpo infrastructure so that I don't have to think about it.

If there is doubt about this let's just do it in two steps:

1. Get hosting for static content (I will run the "build" scripts on my local machine)

2. Setup some other tpo machine that automates the "build" of the static content and pushes it to the repo.

Worth noting that running such makefile is also a requirement for the stem docs: https://trac.torproject.org/projects/tor/ticket/7324.

weasel is rewriting how the mirroring system works so we can handle more static domains like this, and the build requirements. We'll probably be ready in the next few days.

Trac:
Status: new to closed
Resolution: N/A to fixed