Repository navigation
Labels instead of extensions #249
Replies: 1 comment
|
I did and we use extensions instead of unstructured labels as we can provide better user experience with extensions, e.g. more informed validation errors. It's much harder to do with arbitrary key/value string pairs (labels). For extending Caddy, also decided against encoding the Caddyfile as lables as it's arguably more cryptic than just allowing users to use Caddyfiles directly. See comparison in this comment: #107 (comment)
I agree that it might be inconvenient if you're familiar with the configuration of traefic/caddy with labels and got used to them. But given that we anyway provide our own Compose spec interpretation and implementation, we're not limited to using only labels on containers to be able to extend the default Docker Compose capabilities. We can even not prefix them with Has anything specific been confusing with uncloud-specific extensions? Maybe we can improve docs and provide more examples? |
Uh oh!
There was an error while loading. Please reload this page.
Did you consider using labels for port exposure and other features? Like traefik does? It looks more native to me.
All reactions