I think the YAML anchors section would lead to an unparseable compose file? No `...

		dijksterhuis on Aug 16, 2022 \| parent \| context \| favorite \| on: Docker Compose best practices for dev and prod I think the YAML anchors section would lead to an unparseable compose file? No `services` block above the `api` and `web` services, on the same level as `x-app:`. So the `<<: *default-app` anchor won't be recognised as the block that defines it is never terminated prior to use? (I've not tested as currently on the windows gaming box. this is purely from reading it, so happy to be corrected).

Yeah, the example in this blog post is nonsense. The services shouldn't be defined inside the same block as the defaults.