Document `RATTLER_AUTH_FILE`

[wolfv]

You can point RATTLER_AUTH_FILE env var to a JSON file that contains tokens for anaconda/quetz/artifactory/prefix.dev.

The format of the file is the same as what's stored as the "fallback" with rattler. It looks like:

{
    "*.myhost.com": {
        "CondaToken": "mytoken"
    },
    "*.prefix.dev": {
        "BearerToken": "aproperbearer"
    },
    "*.iambasic.com": {
        "BasicHTTP": {
            "username": "myuser",
            "password": "mypass"
        }
    }
}

We should add this to our docs.

The upload subcommand can also use these credentials.

[Krande]

Hey, I'd like to use packages from my custom quetz server on a few different rattler build projects locally. How would I add a custom quetz server as a global package source for all my local projects when using pixi and rattler-build?

I know I can add custom channels by appending -c https://myqetz.com/get/my-channel, but ideally I'd like to have these upstream sources as a global config.

Using conda mambabuild I just add a channel to my .condarc file like so:

channels:
  - https://myquetz.com/get/my-channel
  - conda-forge

I thought perhaps I could add it using the RATTLER_AUTH_FILE, but it seems my rattler-build is still not grabbing packages from my quetz server even though I have specified a json file as shown above with the url of my quetz server.

Any tips would be much appreciated?

Best Regards Kristoffer

[pavelzw]

The auth file is not for specifying channels, only for specifying auth. What you want is https://github.com/prefix-dev/rattler-build/issues/262

@wolfv does rattler-build read pixi's default channel configuration?