Support for generic network #8
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While setting up a new project, I ran into
Apparently from https://stackoverflow.com/a/53838883/455008, this is because Docker caps out at 30 networks. After that and it refuses to work. I thought about deleting old/legacy projects, but that doesn't help things like Jenkins and onboarding.
I think making an internal network at the dev-ops level and just using that network to pivot between php/nginx could work fine. I don't see any immediate concerns for this plan, so pending merge I can cut another release/tag.
So new projects (instead of making their own network) can just define this network as external and use it.