RealDevSquad / RealDevSquad/website-backend

Additional environment variables needed in Staging

Open
#1,082 0 comments 0 reactions 1 assignee View on GitHub

@prakashchoudhary07 is already working on this.

Since May 13, 2023.

dependencies
Dominant language
JavaScript
Stars
74
Forks
276
Avg merge
1d 26m
Merged PRs (30d)
14

Description

The feature create-group-roles and assign-groups requires the following custom variables:

  • Discord base URL of Cloudflare for Athena bot: For making requests, we need the base URL of our Discord bot hosted in Cloudflare workers.
    Variable name: DISCORD_BASE_URL
    Location: website-backend

  • RSA rdsServerlessPrivateKey: For making requests to the discord-bot server, every request must be authenticated with the same key pair that is used to verify in the discord server. Thus, a new key pair with the name RDS_SERVERLESS is necessary for creating new tokens.
    Variable names:

  • RDS_SERVERLESS_PRIVATE_KEY for Website backend

  • RDS_SERVERLESS_PUBLIC_KEY for Cloudflare workers Discord-slash commands

  • rdsServerlessTtl: For expiry of the generated token.
    Variable name: RDS_SERVERLESS_TTL
    Location: website-backend

Environment Variable Name Repository
RDS_SERVERLESS_PRIVATE_KEY WEBSITE BACKEND
RDS_SERVERLESS_PUBLIC_KEY DISCORD SLASH COMMANDS
RDS_SERVERLESS_TTL WEBSITE BACKEND
DISCORD_BASE_URL WEBSITE BACKEND
Specifications of the key:
  • Must be of size 2048.
  • Must start with -----BEGIN RSA PRIVATE KEY-----
    This requirement is because the package @tsndr/cloudflare-worker-jwt package used in the discord-slash-command project has this set of requirements to function.
Updates
  • A RSA key is to be generated and its private key named RDS_SERVERLESS_PRIVATE_KEY is to be set as an environment variable for website-backend.
  • Its corresponding public key, ' RDS_SERVERLESS_PUBLIC_KEY, is to be set as an environment variable for discord-slash-commands` Cloudflare workers.


Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.