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

Update Amazon Keys on Live System #864

Open
mariobehling opened this issue Jul 6, 2019 · 1 comment
Open

Update Amazon Keys on Live System #864

mariobehling opened this issue Jul 6, 2019 · 1 comment
Labels

Comments

@mariobehling
Copy link
Collaborator

All AWS keys were due to an Amazon security policy as there were keys that were deactivated, but not deleted still listed on AWS. Which files need to have a new AWS key?

Please help to list the files where the new keys need to be added for:

  • app
  • upload
  • vr-maven
  • lino
  • vr-main
  • vr-compute
@munen
Copy link
Collaborator

munen commented Jul 6, 2019

This codebase uses the config gem[1] for multi-environment configurations. This yields a file config/settings.yml in the main app[2] and the back-office app[3]. Both show multiple entries for aws keys. The one from the main app would (as commented in the settings.yml file) be overridden on the server itself: app@voicerepublic:~/app/current/config/settings.local.yml.

If you’re looking into how configuration is done in the codebase, theres documentation in the readme: https://github.com/voicerepublic/voicerepublic_dev/blob/integration/README.md#working-with-settingsconfig

  1. https://github.com/railsconfig/config
  2. https://github.com/voicerepublic/voicerepublic_dev/blob/integration/config/settings.yml
  3. https://github.com/voicerepublic/vr-backoffice/blob/bb75305c6724d3cbfd8b24a181ed46f0cf30a006/config/settings.yml

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

No branches or pull requests

2 participants