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

Feat/frontend key access #132

Merged
merged 3 commits into from
Dec 2, 2024
Merged

Feat/frontend key access #132

merged 3 commits into from
Dec 2, 2024

Conversation

cyramic
Copy link
Contributor

@cyramic cyramic commented Nov 28, 2024

This does the following:

  • Removes Frontend hosting on EC2
  • Creates user to allow hosting on Heroku via key
  • Some cleanup

Tested on:

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might need to chat this one through to fully understand what's going on here :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All this is doing is generating the access keys with the required permissions for Heroku so I can copy the result in to Heroku's env vars. :-)

Ideally I would have a setup that doesn't need this and users of the platform would just assume the role directly. That will be for later.

@cyramic cyramic merged commit 5788a15 into main Dec 2, 2024
1 check passed
@cyramic cyramic deleted the feat/frontend-key-access branch December 2, 2024 11:16
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

Successfully merging this pull request may close these issues.

2 participants