How to use package if conda-forge must be accessed through a proxy channel?

[DrChainsaw]

How to use package if conda-forge must be accessed through a proxy channel?

[DrChainsaw]

I managed to get an admin to sit and cross check logs with me and they did something on their side (don't know what exactly) that made it work for me.

Sorry for the noise. Didn't really know where to start with this problem.

[cjdoris]

I'm also not an expert in this aspect of Conda.

From what I can tell, the only problem is with the channel name (conda-forge-proxy instead of conda-forge) and you have the base proxy URL working ok via Conda settings?

From reading about Conda config it doesn't look like there is a setting to rename channels. I'd be happy to add such a setting to CondaPkg - or better still you could make a PR for this feature.

[DrChainsaw]

Great!

I will first try to ask around to see if I can find someone who can tell me if there is some idiomatic solution to this problem within conda. Maybe it for example just is our artifcatory that is misconfigured.

After that I'll look into a PR. I suppose one could add the remapping to the CondaPkg.toml file, but it should probably be some system global config instead since it depends more on the environment where the package is installed to than the package itself. Are there better options than environment variables for this?

[cjdoris]

User preferences in CondaPkg are set using env vars or Julia preferences (https://github.com/JuliaPy/CondaPkg.jl/?tab=readme-ov-file#preferences).

But yeah, ideally you'd just have artifactory set up to use the correct channel names.