@@ -5,33 +5,19 @@ infrastructure team][team] to manage our services. Using some of the tools in
5
5
this repo require privileges only infra team members have.
6
6
7
7
* [ ** ansible** ] ( ansible/README.md ) : Ansible playbooks to deploy our servers
8
- * [ ** azure-configs** ] ( azure-configs/README.md ) : shared CI templates for Azure
9
- Pipelines
10
8
* [ ** aws-creds** ] [ aws-2fa ] : log into AWS with two factor authentication
11
9
* [ ** github-actions** ] ( github-actions/README.md ) : shared actions for GitHub
12
10
Actions
13
- * [ ** restart-rcs** ] ( #restart-rcs ) : redeploying [ rust-central-station] [ rcs ]
14
11
* [ ** setup-deploy-keys** ] ( #setup-deploy-keys ) : automation for GitHub deploy keys
15
12
* [ ** terraform** ] ( terraform/shared/README.md ) : Terraform configuration to deploy our
16
13
cloud resources
17
- * [ ** travis-configs** ] ( travis-configs/README.md ) : shared importable config
18
- files for Travis CI
19
14
* [ ** with-rust-key** ] ( #with-rust-key ) : execute commands using the Rust release
20
15
signing key
21
16
22
17
The contents of this repository are released under the MIT license.
23
18
24
19
[ aws-2fa ] : https://forge.rust-lang.org/infra/docs/aws-access.html#2-factor-authentication
25
20
[ team ] : https://github.com/rust-lang/infra-team
26
- [ rcs ] : https://github.com/rust-lang/rust-central-station
27
-
28
- ## restart-rcs
29
-
30
- The ` restart-rcs.sh ` script redeploys [ rust-central-station] [ rcs ] by pulling
31
- the latest container image and recreating the container on the server. You need
32
- to have SSH access to the server (the script tries to log into the
33
- ` rcs.rust-lang.org ` host) and AWS credentials locally to pull the image from
34
- ECR.
35
21
36
22
## setup-deploy-keys
37
23
@@ -49,14 +35,11 @@ cargo run --bin setup-deploy-keys org-name/repo-name
49
35
50
36
The tool will generate a key, upload it to GitHub and then print an environment
51
37
variable ` GITHUB_DEPLOY_KEY ` containing an encoded representation of the
52
- private key. It will also try to add the key to Travis CI if you have the
53
- ` TRAVIS_TOKEN ` variable set to [ your Travis CI API token] [ travis-token ] .
38
+ private key.
54
39
55
40
To use the key the easiest way is to cd into the directory you want to deploy,
56
41
[ download this rust program] [ setup-deploy-keys-deploy ] , compile and run it
57
- (with the ` GITHUB_DEPLOY_KEY ` variable set). There are importable configuration
58
- snippets available for [ Azure Pipelines] [ setup-deploy-keys-azure ] and [ Travis
59
- CI] [ setup-deploy-keys-travis ] .
42
+ (with the ` GITHUB_DEPLOY_KEY ` variable set).
60
43
61
44
By default the tool generates ed25519 keys, but some libraries (like ` git2 ` )
62
45
don't support them yet. In those cases you can generate RSA keys by passing the
@@ -66,10 +49,7 @@ don't support them yet. In those cases you can generate RSA keys by passing the
66
49
cargo run --bin setup-deploy-keys org-name/repo-name --rsa
67
50
```
68
51
69
- [ travis-token ] : https://travis-ci.com/account/preferences
70
52
[ setup-deploy-keys-deploy ] : https://raw.githubusercontent.com/rust-lang/simpleinfra/master/setup-deploy-keys/src/deploy.rs
71
- [ setup-deploy-keys-azure ] : https://github.com/rust-lang/simpleinfra/tree/master/azure-configs#static-websitesyml
72
- [ setup-deploy-keys-travis ] : https://github.com/rust-lang/simpleinfra/blob/master/travis-configs/static-websites.yml
73
53
74
54
## with-rust-key
75
55
0 commit comments