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

[Maintenance] Decoupling of stack for refarch and refarch-templates #170

Closed
2 tasks done
devtobi opened this issue Sep 18, 2024 · 0 comments · Fixed by #171
Closed
2 tasks done

[Maintenance] Decoupling of stack for refarch and refarch-templates #170

devtobi opened this issue Sep 18, 2024 · 0 comments · Fixed by #171
Assignees
Labels
Priority: High The issue contains work with high priority. Type: Maintenance The issue contains maintenance work.

Comments

@devtobi
Copy link
Member

devtobi commented Sep 18, 2024

Relevant component

No response

Problem description (optional)

Currently we try to mimic the stack of https://github.com/it-at-m/refarch-templates by providing a "copy" of the docker-compose file as a docker-compose-refarch-base.yml
However this assumes we will try to keep both stacks in sync in the future (which has to be done manually).
Since the development for the gateway and the integrations itself don't need the same setup as when working with the templates, we should decouple those stacks and handle them separately.

Desired solution

Merge docker-compose-refarch-base.yml and docker-compose.yml and only keep relevant images for development.

Considered alternatives (optional)

No response

Additional context (optional)

No response

No duplicate

  • I confirm that this issue is not a duplicate

Code of Conduct

  • I agree to follow this project's Code of Conduct
@devtobi devtobi added Priority: High The issue contains work with high priority. Type: Maintenance The issue contains maintenance work. labels Sep 18, 2024
@devtobi devtobi moved this from Open to Accepted in it@M RefArch Sep 18, 2024
@github-project-automation github-project-automation bot moved this from Accepted to Done in it@M RefArch Sep 18, 2024
@devtobi devtobi self-assigned this Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High The issue contains work with high priority. Type: Maintenance The issue contains maintenance work.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant