Infrastructure

Servo's infrastructure is managed with SaltStack. Issues directly related to to the infrastructure's configuration should be filed on the SaltFS repo.

General infrastructure issues are filed under the A-Infrastructure tag in the main Servo issue tracker.

DNS

Servo's DNS and SSL are managed through CloudFlare. Credentials for logging into CloudFlare are in the doc with all the other secrets. DNS entries are accessed by clicking the blue square labeled "DNS" in the row of blue squares near the top of the page.

AWS S3 file hosting

We use S3 to host nightlies and the downloads page. The servo-builds bucket can be accessed directly at http://servo-builds.s3-website-us-west-2.amazonaws.com/. Due to redirection silliness, the buckets download.servo.org and dl.servo.org exist. Their sole purpose is to redirect traffic to the servo-builds bucket in the way that AWS demands; nobody can nor should upload any files to them ever.

The "Servo Developer Preview Downloads" page on S3 is raw HTML, CSS, and bootstrap yanked from the servo.org main page in June 2016. Edit it by downloading the HTML, making changes, and re-uploading to the servo-builds S3 bucket (sorry!)

Other Links

General information about the project's infrastructure goes in this wiki and should be linked from this list:

• Adding a repo to Homu
• Homu UI
• Updating the Rust compiler used by Servo
• Buildbot administration - has list of IPs
• Buildbot UI
• SaltStack Administration
• Servo's Highfive
• Servo's Crowbot
• Removing push notifications from IRC hooks