https://github.com/rust-lang/rust-central-station

Old home of some infra pieces
https://github.com/rust-lang/rust-central-station

Last synced: 4 months ago
JSON representation

Old home of some infra pieces

• Host: GitHub
• URL: https://github.com/rust-lang/rust-central-station
• Owner: rust-lang
• License: apache-2.0
• Archived: true
• Created: 2017-01-26T18:34:49.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2020-11-25T17:55:20.000Z (about 4 years ago)
• Last Synced: 2024-09-25T20:14:04.464Z (4 months ago)
• Language: Rust
• Homepage:
• Size: 2.2 MB
• Stars: 74
• Watchers: 11
• Forks: 52
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE-APACHE

Awesome Lists containing this project

README

        
# Archived repository!

This repository was the home of some of the most important services hosted by

the Rust Infrastructure Team, but over time those services were moved to new

homes:

* The release process is now developed and deployed in [rust-lang/promote-release].

* Bors is now developed, configured and deployed in [rust-lang/homu].

* Team synchronization is now developed and deployed in [rust-lang/sync-team].

* Cancelbot is not in use anymore.

[rust-lang/promote-release]: https://github.com/rust-lang/promote-release

[rust-lang/homu]: https://github.com/rust-lang/homu

[rust-lang/sync-team]: https://github.com/rust-lang/sync-team

# Rust Central Station

Or otherwise just another name for the old buildmaster.

This repo is hooked up to an automated docker build

* https://hub.docker.com/r/alexcrichton/rust-central-station/

On the destination machine you can run it as:

    ./run-prod.sh

Services currently provided are:

* cancelbot for rust-lang/rust

* cancelbot for rust-lang/cargo

* homu

* nginx in front of homu

* ssl via letsencrypt

Future services

* signing Rust releases

## Architecture

This is intended to be run as a container on the destination server, so the

container here specifies everything about what's being run.

* Secrets are stored in `secrets.toml` next to `secrets.toml.example` and are

  shared with the container.

* Programs are provided in the container (`tq` and `rbars`) which will read the

  TOML configuration for use in shell scripts.

* Everything pipes output to `logger` to collect output

* Services are just run as simple daemons, not a lot of management.