Closed yelizariev closed 4 years ago
Yes, it's because in a single server there might be several odoo instances, but just one inverseproxy. Also it is only useful for test/prod environments. Also some people would still prefer nginx/apache/etc.
So it's not included on purpose.
My concern is mostly about the fact, that the file content has to be copy-pasted from the documentation.
Doodba-scaffolding already has traefik configuration related to the inverseproxy file
so, it should be a good place for the file. Though, I understand the idea to keep here files for a single project only (while inverseproxy could be used on top of multiple projects)
It would be more useful to have another project about handling the inverse proxy thing. But that would fit better an ansible role or something like that.
The labels you point are there to make the scaffolding compatible out of the box with the provided traefik settings, but still these are separate pieces of the puzzle.
Thanks for your understanding.
Is there special reason, why
inverproxy.yaml
file is not in scaffolding? If this will be merged, I'd make corresponding updates in doodba's README