You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deploying internal conda packages my usual practice has been to namespace channels by their respective team name (which also corresponds to their organisation name in our GitHub Enterprise Server) - e.g. retail/dev, retail/prod
It appears this isn't supported when creating a channel:
In my own implementation the namespaces were implemented as physical folders. If the backend storage supports folders that might also be possible in quetz?
Alternatively, I guess the channel name could be url-encoded in the backend... so long as that was transparent to the user
i.e. I'd want the UX to be mamba install -c seau/dev my-package not mamba install seau%2Fdev my-package
When deploying internal conda packages my usual practice has been to namespace channels by their respective team name (which also corresponds to their organisation name in our GitHub Enterprise Server) - e.g.
retail/dev
,retail/prod
It appears this isn't supported when creating a channel:
quetz/quetz/tasks/indexing.py
Lines 271 to 274 in 6cdf96e
The text was updated successfully, but these errors were encountered: