Skip to content

Improve Docker Compose handling#230

Open
bartmkraus wants to merge 2 commits intodevelopfrom
bartek/improve-docker-compose-handling
Open

Improve Docker Compose handling#230
bartmkraus wants to merge 2 commits intodevelopfrom
bartek/improve-docker-compose-handling

Conversation

@bartmkraus
Copy link
Copy Markdown
Member

Comment thread .circleci/config.yml
- run:
name: Copy base docker-compose
command: |
cp ../docker-compose.base.yml ./docker-compose.base.yml
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This won't ever work. CI is not working in scope of full_stack repo.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yes, this caught me off guard and I haven't come up with a solution yet. But as you mentioned in another comment, having the docker-compose.yml only in the full stack repo would make it very difficult to implement proper CI and testing. It would require some bash scripts which will add extra overhead in terms of their maintenance.

Comment thread docker-compose.yml
- db
db:
extends:
file: ../docker-compose.base.yml
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This would be okay approach with monorepo, but not really with current wonky git submodules approach.
Maybe it'd be better to have whole docker-compose.yml in full stack repo, but then again - CI and testing would become more complex.

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