Delete the outdated MinIO quickstart (#56509)
This commit is contained in:
Sam Browning
@@ -11,6 +11,7 @@ topics:
|
||||
shortTitle: Enable Packages with MinIO
|
||||
redirect_from:
|
||||
- /admin/packages/enabling-github-packages-with-minio
|
||||
- /admin/configuring-packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
|
||||
---
|
||||
|
||||
> [!WARNING]
|
||||
@@ -21,7 +22,7 @@ redirect_from:
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your MinIO storage bucket. To help you quickly set up a MinIO bucket and navigate MinIO's customization options, see the [AUTOTITLE](/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages).
|
||||
Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your MinIO object store. See the [MinIO AIStor Documentation](https://docs.min.io/enterprise/aistor-object-store/).
|
||||
|
||||
Ensure your MinIO external storage access key ID and secret have these permissions:
|
||||
* `s3:PutObject`
|
||||
|
||||
@@ -14,10 +14,8 @@ children:
|
||||
- /enabling-github-packages-with-aws
|
||||
- /enabling-github-packages-with-azure-blob-storage
|
||||
- /enabling-github-packages-with-minio
|
||||
- /quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
|
||||
- /configuring-package-ecosystem-support-for-your-enterprise
|
||||
- /migrating-your-enterprise-to-the-container-registry-from-the-docker-registry
|
||||
shortTitle: Packages
|
||||
---
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %}
|
||||
|
||||
@@ -1,131 +0,0 @@
|
||||
---
|
||||
title: Quickstart for configuring your MinIO storage bucket for GitHub Packages
|
||||
intro: 'Configure your custom MinIO storage bucket for use with {% data variables.product.prodname_registry %}.'
|
||||
versions:
|
||||
ghes: '*'
|
||||
type: quick_start
|
||||
topics:
|
||||
- Packages
|
||||
- Enterprise
|
||||
- Storage
|
||||
shortTitle: Quickstart for MinIO
|
||||
redirect_from:
|
||||
- /admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
|
||||
---
|
||||
|
||||
{% data reusables.package_registry.packages-ghes-release-stage %}
|
||||
|
||||
Before you can enable and configure {% data variables.product.prodname_registry %} on {% data variables.location.product_location_enterprise %}, you need to prepare your third-party storage solution.
|
||||
|
||||
MinIO offers object storage with support for the S3 API and {% data variables.product.prodname_registry %} on your enterprise.
|
||||
|
||||
This quickstart shows you how to set up MinIO using Docker for use with {% data variables.product.prodname_registry %} but you have other options for managing MinIO besides Docker. For more information about MinIO, see the official [MinIO docs](https://docs.min.io/).
|
||||
|
||||
## 1. Choose a MinIO mode for your needs
|
||||
|
||||
| MinIO mode | Optimized for | Storage infrastructure required |
|
||||
|----|----|----|
|
||||
| Standalone MinIO (on a single host) | Fast setup | Not applicable |
|
||||
| Clustered MinIO (also called Distributed MinIO)| Data security | Storage servers running in a cluster |
|
||||
|
||||
For more information about your options, see the official [MinIO docs](https://docs.min.io/).
|
||||
|
||||
## 2. Install, run, and sign in to MinIO
|
||||
|
||||
1. Set up your preferred environment variables for MinIO.
|
||||
|
||||
These examples use `MINIO_DIR`:
|
||||
|
||||
```shell
|
||||
export MINIO_DIR=$(pwd)/minio
|
||||
mkdir -p $MINIO_DIR
|
||||
```
|
||||
|
||||
1. Install MinIO.
|
||||
|
||||
```shell
|
||||
docker pull minio/minio
|
||||
```
|
||||
|
||||
For more information, see the official [MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide).
|
||||
|
||||
1. Sign in to MinIO using your MinIO access key and secret.
|
||||
|
||||
{% linux %}
|
||||
|
||||
```shell
|
||||
$ export MINIO_ACCESS_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
|
||||
# this one is actually a secret, so careful
|
||||
$ export MINIO_SECRET_KEY=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
|
||||
```
|
||||
|
||||
{% endlinux %}
|
||||
|
||||
{% mac %}
|
||||
|
||||
```shell
|
||||
$ export MINIO_ACCESS_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
|
||||
# this one is actually a secret, so careful
|
||||
$ export MINIO_SECRET_KEY=$(cat /dev/urandom | LC_CTYPE=C tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1)
|
||||
```
|
||||
|
||||
{% endmac %}
|
||||
|
||||
You can access your MinIO keys using the environment variables:
|
||||
|
||||
```shell
|
||||
echo $MINIO_ACCESS_KEY
|
||||
echo $MINIO_SECRET_KEY
|
||||
```
|
||||
|
||||
1. Run MinIO in your chosen mode.
|
||||
|
||||
* Run MinIO using Docker on a single host:
|
||||
|
||||
```shell
|
||||
$ docker run -p 9000:9000 \
|
||||
-v $MINIO_DIR:/data \
|
||||
-e "MINIO_ACCESS_KEY=$MINIO_ACCESS_KEY" \
|
||||
-e "MINIO_SECRET_KEY=$MINIO_SECRET_KEY" \
|
||||
minio/minio server /data
|
||||
```
|
||||
|
||||
For more information, see [MinIO Docker Quickstart guide](https://docs.min.io/docs/minio-docker-quickstart-guide.html).
|
||||
|
||||
* Run MinIO using Docker as a cluster. This MinIO deployment uses several hosts and MinIO's erasure coding for the strongest data protection. To run MinIO in a cluster mode, see the [Distributed MinIO Quickstart Guide](https://docs.min.io/docs/distributed-minio-quickstart-guide.html).
|
||||
|
||||
## 3. Create your MinIO bucket for {% data variables.product.prodname_registry %}
|
||||
|
||||
1. Install the MinIO client.
|
||||
|
||||
```shell
|
||||
docker pull minio/mc
|
||||
```
|
||||
|
||||
1. Create a bucket with a host URL that {% data variables.product.prodname_ghe_server %} can access.
|
||||
|
||||
* Local deployments example:
|
||||
|
||||
```shell
|
||||
export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @localhost:9000"
|
||||
docker run minio/mc BUCKET-NAME
|
||||
```
|
||||
|
||||
This example can be used for MinIO standalone.
|
||||
|
||||
* Clustered deployments example:
|
||||
|
||||
```shell
|
||||
export MC_HOST_minio="http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY} @minioclustername.example.com:9000"
|
||||
docker run minio/mc mb packages
|
||||
```
|
||||
|
||||
## Next steps
|
||||
|
||||
To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL:
|
||||
|
||||
```shell
|
||||
echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000"
|
||||
```
|
||||
|
||||
For the next steps, see [AUTOTITLE](/admin/packages/enabling-github-packages-with-minio).
|
||||
@@ -88,7 +88,6 @@ includeGuides:
|
||||
- /admin/managing-your-enterprise-account/about-enterprise-accounts
|
||||
- /admin/getting-started-with-enterprise/about-upgrades-to-new-releases
|
||||
- /admin/configuring-packages/configuring-package-ecosystem-support-for-your-enterprise
|
||||
- /admin/configuring-packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages
|
||||
- /admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/about-pre-receive-hooks
|
||||
- /admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment
|
||||
- /admin/enforcing-policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script
|
||||
|
||||
Reference in New Issue
Block a user