Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add required environment variables for STAGING #52

Closed
4 tasks
Ajeyakrishna-k opened this issue Jan 10, 2024 · 4 comments
Closed
4 tasks

Add required environment variables for STAGING #52

Ajeyakrishna-k opened this issue Jan 10, 2024 · 4 comments
Assignees

Comments

@Ajeyakrishna-k
Copy link
Contributor

Ajeyakrishna-k commented Jan 10, 2024

Add required environment variables for PRODUCTION

Please make these changes after merging these PR:

Following keys need to be added:

  • In Cron jobs Github Settings environment:

    • DISCORD_BOT_PRIVATE_KEY (add the previous private key used in rds backend for backward compatilbility
    • DISCORD_SERVICE_PRIVATE_KEY (newly generated private key)
    • FF_SELF_PRIVATE_KEY with value: 'true'
  • In Discord slash commands Github Settings environment:

    • CRON_JOBS_PUBLIC_KEY (newly generated public key)

Steps to generate private public keys:

Generate private key using : ssh-keygen -t rsa -P "" -b 2048 -m PEM -f jwtRS256.key
View public key using : ssh-keygen -f jwtRS256.key.pub -e -m pkcs8

@Ajeyakrishna-k Ajeyakrishna-k changed the title Add required environment variables for cron jobs STAGING Add required environment variables for STAGING Jan 10, 2024
@prakashchoudhary07
Copy link
Contributor

Updated the configs, thanks for the details

@Ajeyakrishna-k
Copy link
Contributor Author

Ajeyakrishna-k commented Jan 27, 2024

  • In Cron jobs Github Settings environment:

    • DISCORD_BOT_PRIVATE_KEY (add the previous private key used in rds backend for backward compatilbility
    • DISCORD_SERVICE_PRIVATE_KEY (newly generated private key)
    • FF_SELF_PRIVATE_KEY with value: 'true'

@prakashchoudhary07
Copy link
Contributor

prakashchoudhary07 commented Jan 29, 2024

@Ajeyakrishna-k For now we will make changes,
We should always create new tickets for making changes, next time please don't reopen closed tickets,

@prakashchoudhary07
Copy link
Contributor

Thanks for the details, this has been done 💀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants