generated from coop-cloud/example
Pass through AWS_SECRET_ACCESS_KEY #37
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/missing-aws-key-env"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Previously I forgot to add the bits to pass
AWS_SECRET_ACCESS_KEYsecret through - as mastodon can't natively readAWS_SECRET_ACCESS_KEY_FILEit needs to be included using thefile_envtechnique.This is similar to how it is in the hometown recipe, and if you don't have
AWS_SECRET_ACCESS_KEYorAWS_SECRET_ACCESS_KEY_FILEit won't cause an error (tried it locally).I've chaos deployed it to bath.social and it fixed my issue. The symptom was that it seemed to be working, but I looked up an external users profile and it gave a 500 error with this message in the log:
Added a couple of potential reviewers, hope thats ok!
lgtm!
I also noticed the recipe has maintainers, I was about to nag the community on Matrix lol
Still happy to be added as a reviewer anytime <3
Ah yeah, I hadn't noticed the official maintainer bit. Maybe we should also both add ourselves to that list? I'll do it if you do... (is there some process there?).