Skip to content

Commit 393f0be

Browse files
authored
[HUD] Update README with info about getting access to Vercel (#6098)
As in title
1 parent cf2a379 commit 393f0be

File tree

2 files changed

+8
-3
lines changed

2 files changed

+8
-3
lines changed

torchci/.env.example

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
1-
# Copy this file to .env.local and add keys based on the instructions.
2-
# Ask @suo if you don't know how to get any of these things.
1+
# Copy this file to .env.local and add keys based on the instructions. All of
2+
# these keys can be found on Vercel. Please see the README about getting access
3+
# to Vercel.
34

45
# Rockset API key for talking to our data backend. You can generate one from the
56
# Rockset console (https://console.rockset.com/apikeys).

torchci/README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,11 @@ Here is a checklist of all the different services used by the HUD. Ask
66
@janeyx99 or @suo for help getting access to these services.
77

88
- [Rockset](https://rockset.com/): primary data and metrics backend.
9-
- [Vercel](https://vercel.com/): hosting the website.
9+
- [Vercel](https://vercel.com/): hosting the website. If you are a metamate,
10+
make a post [like
11+
this](https://fb.workplace.com/groups/osssupport/posts/27574509675504286) in the
12+
[Open Source - Support](https://fb.workplace.com/groups/773769332671684) group
13+
to get access to Vercel.
1014
- [Sematext](https://sematext.com/): log drain for our Vercel instance.
1115
- [AWS](http://aws.com/): data pipelines for populating Rockset, Lambda, S3, etc.
1216

0 commit comments

Comments
 (0)