docs: Add S3 documentation #2835
Open
+286
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
delsner
reviewed
Jan 5, 2025
| channels = ["s3://my-bucket/custom-channel"] | ||
| ``` | ||
|
|
||
| In the bucket, you need to have the following structure: |
There was a problem hiding this comment.
Suggested change
| In the bucket, you need to have the following structure: | |
| In the bucket, your objects need to adhere to the standard conda repository structure: |
| custom-channel/ | ||
| noarch/ | ||
| repodata.json | ||
| ... |
Comment on lines
+23
to
+24
| - Using AWS credentials from environment variables, AWS configuration files, ... like in any other AWS tool | ||
| - Using pixi's configuration in combination with storing the credentials in pixi's authentication storage |
There was a problem hiding this comment.
Suggested change
| - Using AWS credentials from environment variables, AWS configuration files, ... like in any other AWS tool | |
| - Using pixi's configuration in combination with storing the credentials in pixi's authentication storage | |
| 1. Using AWS credentials from environment variables or AWS configuration files, like in any other AWS tool | |
| 2. Using pixi's configuration in combination with storing the credentials in pixi's authentication storage |
| - Using pixi's configuration in combination with storing the credentials in pixi's authentication storage | ||
|
|
||
| !!! warning "" | ||
| This is an either/or situation. |
There was a problem hiding this comment.
Suggested change
| This is an either/or situation. | |
| These two options are mutually exclusive! |
| !!! warning "" | ||
| This is an either/or situation. | ||
| Specifying `s3-options` (see below) will deactivate the AWS credentials fetching. | ||
| You can either use the AWS credentials (by not specifying `s3-options`) or from pixi's authentication storage (by specifying `s3-options`). |
There was a problem hiding this comment.
Suggested change
| You can either use the AWS credentials (by not specifying `s3-options`) or from pixi's authentication storage (by specifying `s3-options`). | |
| You can either use the AWS credentials from the conventional locations (by not specifying `s3-options`) or from pixi's authentication storage (by specifying `s3-options`). |
| ## Using pixi's configuration | ||
|
|
||
| You can specify the `project.s3-options` in your `pixi.toml` file. | ||
| This might be especially useful if you want to use a custom S3-compatible host and not use AWS's configuration. |
There was a problem hiding this comment.
Suggested change
| This might be especially useful if you want to use a custom S3-compatible host and not use AWS's configuration. | |
| This might be useful when you want to use a custom S3-compatible host and not AWS's configuration. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
follow-up of #2825, xref conda/rattler#960
cc @olivier-lacroix, @delsner, @moritzwilksch, @ruben-arts, @baszalmstra, @wolfv
Please take a look at this implementation and tell me what you think of it