How to get service compatibility v1.18 *and* v1.19+ (networks) #3514
Unanswered
jonaseberle
asked this question in
Q&A
Replies: 1 comment 3 replies
-
Another step would be to rename "ddev" back to "ddev_default". Then the network itself wouldn't have to be created. Obviously I didn't know how disruptive that name change would be. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Being able to prepare services that won't break ddev with v1.19 will be a huge help.
I'll open this thread here to play with ideas and have people test what we can come up with.
With #3510 there will be a better message to tell users that services need to be upgraded.
This also signals that we are requiring at least networks "default" + "ddev" on all services now to have an easier time detecting a missing upgrade and with supporting problems.
I have tried to make services "v1.19-ready" in v1.18 already and this is what I have come up with:
In your
docker-compose.<service>.yaml
:In your
.ddev/config.yaml
:This is only tested on Linux though. I would be happy to get some feedback if we would need changes in your environment.
A note for testing: Run
ddev start
twice since I might have found a problem where changes to .yaml files are only picked up the second time.Beta Was this translation helpful? Give feedback.
All reactions