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.

Sign up for GitHub

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

Jump to bottom

Move AWS and Vercel sensitive values to "Production" environment #38

Open
PaulRBerg opened this issue Mar 8, 2025 · 0 comments
Open

Move AWS and Vercel sensitive values to "Production" environment #38

PaulRBerg opened this issue Mar 8, 2025 · 0 comments
Assignees
@PaulRBerg @gavriliumircea
Labels
effort: low Easy or tiny task that takes less than a day. priority: 1 This is important. It should be dealt with shortly. type: build Changes that affect the build system or external dependencies. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.

Comments

@PaulRBerg
Copy link
Member

  • AWS_ACCESS_KEY_ID
  • AWS_ACCOUNT_ID
  • AWS_REGION
  • AWS_SECRET_ACCESS_KEY
  • ECS_CLUSTER
  • ECS_SERVICE
  • VERCEL_PROJECT_ID
  • VERCEL_TOKEN
@PaulRBerg PaulRBerg added effort: low Easy or tiny task that takes less than a day. priority: 1 This is important. It should be dealt with shortly. type: build Changes that affect the build system or external dependencies. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise. labels Mar 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@PaulRBerg PaulRBerg

@gavriliumircea gavriliumircea

Labels
effort: low Easy or tiny task that takes less than a day. priority: 1 This is important. It should be dealt with shortly. type: build Changes that affect the build system or external dependencies. work: complicated Sense-analyze-respond. The relationship between cause and effect requires analysis or expertise.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@PaulRBerg @gavriliumircea