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

Fix Docker-Compose Setup on AWS #217

Open
phildree opened this issue Jul 12, 2023 · 1 comment
Open

Fix Docker-Compose Setup on AWS #217

phildree opened this issue Jul 12, 2023 · 1 comment

Comments

@phildree
Copy link
Contributor

User story

  1. As a developer
  2. I want a running test setup on aws
  3. So that I can test if everything works and scales as expected

Acceptance criteria

  • working docker-compose setup for aws

Definition of done (DoD)

  • Feature is done when the acceptance criteria are fullfiled
  • Feature is done when there are test where it is necessary and they pass
  • Feature is done when the linter passes
  • Feature is done when it is merged onto our main branch (after the code has been reviewed by at least one other person)
  • Feature is done when the code has been documentend or commented properly

DoD general criteria

  • Feature has been fully implemented
  • Feature has been merged into the mainline
  • All acceptance criteria were met
  • Product owner approved features
  • All tests are passing
  • Developers agreed to release
@phildree phildree added Implementation Prio: Low Backend Item for the Backend-Team labels Jul 12, 2023
@phildree phildree moved this to Product Backlog in amos2023ss01-feature-board Jul 12, 2023
@phildree phildree moved this from Product Backlog to Sprint Backlog in amos2023ss01-feature-board Jul 12, 2023
@jnsrnhld
Copy link
Contributor

@ahaverkamp Without killing the images on the running instances, I can only try to remember how the problem did look like.
It was something related to the backend-service and demodata-aws service. If I'm not mistaken, the backend service has no attached profile in the setup.yaml and this caused the issue.

If this does not help I'll kill the containers and copy the error message.

@ahaverkamp ahaverkamp moved this from Sprint Backlog to In Progress in amos2023ss01-feature-board Jul 12, 2023
@ahaverkamp ahaverkamp self-assigned this Jul 12, 2023
@ahaverkamp ahaverkamp moved this from In Progress to Awaiting Review in amos2023ss01-feature-board Jul 12, 2023
@phildree phildree moved this from Awaiting Review to Feature Archive in amos2023ss01-feature-board Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Feature Archive
Development

No branches or pull requests

3 participants