- Create a new Discord bot in the developer portal
- Fork the repository
- Clone your fork to your computer
- If you'd like to get a tour of the codebase and a second pair of eyes during setup, snag a slot on the calendar
- Copy
.env.example
to.env
- Configure env variable
- From the General Information page:
- From the Bot page:
- (optional) Request access token for Amplitude metrics from vcarl#7694 and paste the token as
AMPLITUDE_KEY
- (optional) Go to your Github Settings and create a personal access token with the scope "gist", and paste the
- From the Bot page: 3 settings off, 2 settings on
- Public Bot off
- Requires OAuth2 Code Grant off
- Presence Intent off
- Server Members Intent on
- Message Content Intent on
npm install
npm run dev
- Look for the following message in the logs, and open the URL in a browser where you're logged into Discord.
Bot started. If necessary, add it to your test server:
- Make sure to not install this bot directly on Reactiflux but on the Reactiflux Test Server. Ask for the correct role in RF's #reactibot channel
There are subtle issues when making some chaings. These are notes for steps to take to make sure it's done correctly when needed.
Generating images for #resume-review requires GraphicsMagick installed. Brew, Linux
Adding a new environment variable needs to be done in several places to work corectly and be predictable for new developers:
- Add a suitable example to
.env.example
- Add to your own
.env
(and restart the dev server) - Add to the action in
.github/workflows/node.js.yml
- Add to the Kubernetes config under `cluster/deployment.yml