GITBOOK-57: FR-865: Bucket name needs a /

This commit is contained in:
Hannah Cooper
2025-12-21 20:58:29 +00:00
committed by gitbook-bot
parent 73a44bb7b4
commit 137e20faef
9 changed files with 10 additions and 10 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 186 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 220 KiB

View File

@@ -41,7 +41,7 @@ Select **Docker Standalone** then click **Start Wizard**. Then select the **Edge
| Name | Enter a name for your environment. |
| Portainer API server URL | Enter the URL and port of your Portainer Server instance as it will be seen from your Edge environment. If using a FQDN, ensure that DNS is properly configured to provide this. |
<figure><img src="/broken/files/9cqG768bKKshymxybpuv" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../../.gitbook/assets/2.18-environments-add-docker-edge-async-name (1).png" alt=""><figcaption></figcaption></figure>
As an optional step you can expand the **More settings** section and adjust the **Ping**, **Snapshot** and **Command** intervals for the environment - this defines how often this Edge Agent will check in with the Portainer Server for status updates, snapshot updates and to see if there are new pending commands to run, respectively. The default for each is once a minute, but the defaults can be adjusted in the [Edge Compute settings](../../../settings/edge.md#async-check-in-intervals).&#x20;

View File

@@ -41,7 +41,7 @@ Select **Podman** then click **Start Wizard**. Then select the **Edge Agent Asyn
| Name | Enter a name for your environment. |
| Portainer API server URL | Enter the URL and port of your Portainer Server instance as it will be seen from your Edge environment. If using a FQDN, ensure that DNS is properly configured to provide this. |
<figure><img src="/broken/files/9cqG768bKKshymxybpuv" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../../.gitbook/assets/2.18-environments-add-docker-edge-async-name (1).png" alt=""><figcaption></figcaption></figure>
As an optional step you can expand the **More settings** section and adjust the **Ping**, **Snapshot** and **Command** intervals for the environment - this defines how often this Edge Agent will check in with the Portainer Server for status updates, snapshot updates and to see if there are new pending commands to run, respectively. The default for each is once a minute, but the defaults can be adjusted in the [Edge Compute settings](../../../settings/edge.md#async-check-in-intervals).&#x20;

View File

@@ -164,12 +164,12 @@ Select **Store in S3** and fill in the options, using the below as a guide.
| Access Key ID | Enter the access key ID for your S3 bucket. |
| Secret Access Key | Enter the secret key for your S3 bucket. |
| Region | Enter the region where your bucket is located (for example, `us-west-1`). |
| Bucket name | Enter the name of your S3 bucket. |
| Bucket name | <p>Enter the name of your S3 bucket. <br>Note that if you include a folder path in the Bucket name field, the prefix must end with a trailing slash.</p> |
| S3 compatible host | If you are using a non-AWS S3-compatible provider (such as MinIO), enter the URL (including the protocol and port if necessary) here. If you're using AWS S3, leave this blank. |
| Password protect | Enable this to protect your backups with a password. |
| Password | Enter the password to set on your backups. |
<figure><img src="../../.gitbook/assets/2.17-admin-settings-backup-s3.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../../.gitbook/assets/take-a-backup.png" alt=""><figcaption></figcaption></figure>
### Restoring from a local file
@@ -194,12 +194,12 @@ Restoring a configuration is only possible on a fresh instance of Portainer duri
| Access key ID | Enter the access key ID for your S3 bucket. |
| Secret access key | Enter the secret key for your S3 bucket. |
| Region | Enter the region where your bucket is located (for example, `us-west-1`). |
| Bucket name | Enter the name of your S3 bucket. |
| Bucket name | <p>Enter the name of your S3 bucket. <br>Note that if you include a folder path in the Bucket name field, the prefix must end with a trailing slash.</p> |
| S3 Compatible Host | If you are using a non-AWS S3-compatible provider (such as MinIO), enter the URL (including the protocol and port if necessary) here. If you're using AWS S3, leave this blank. |
| Filename | Enter the filename of the backup you want to restore. |
| Password | Enter the password set on your backup (if any). |
<figure><img src="../../.gitbook/assets/2.17-admin-settings-backup-s3-restore.png" alt=""><figcaption></figcaption></figure>
<figure><img src="../../.gitbook/assets/restore-from-backup.png" alt=""><figcaption></figcaption></figure>
When you're ready, click **Restore Portainer**. The restore might take a few moments. When it has finished, you will be redirected to the login page. You can now log in with your previous credentials and your previous configuration will be restored.

View File

@@ -59,7 +59,7 @@ To add a new credential, click the **Add git credential** button and fill out th
| Username | Enter the username, if relevant. |
| Personal Access Token | Enter the personal access token. |
<figure><img src="/broken/files/nJsNFlKSiOkomPKUgwMN" alt=""><figcaption></figcaption></figure>
<figure><img src="../.gitbook/assets/2.33-account-git-creds-new.png" alt=""><figcaption></figcaption></figure>
Once you've entered the relevant details, click **Save git credential** to save the entry.

View File

@@ -12,7 +12,7 @@ This method lets you pull images from Docker Hub or from another registry that y
From the menu select **Images**. Select the registry to use then enter the name of the image. On a multi-node environment, select the node to deploy to.
<figure><img src="/broken/files/0gsoANgVX6ylmlLvlYkk" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../.gitbook/assets/2.15-docker_images_pull_images (1).png" alt=""><figcaption></figcaption></figure>
When you're ready, click **Pull the image**.

View File

@@ -14,7 +14,7 @@ In this section you can:
* View the [service logs](logs.md).
* Update, [roll back](rollback.md) or delete the service.
<figure><img src="/broken/files/3LlEyQXwKwwHMUYOkLzN" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../.gitbook/assets/2.15-docker_services_service_details (1).png" alt=""><figcaption></figcaption></figure>
## Container specification configuration options

View File

@@ -78,7 +78,7 @@ You can also toggle the stack [webhook](webhooks.md) and retrieve the webhook UR
You can choose to **Prune services** if you have made changes that remove some services from the stack.
<figure><img src="/broken/files/5cu2Q9GNn6Gzxrb7wVP1" alt=""><figcaption></figcaption></figure>
<figure><img src="../../../.gitbook/assets/2.20-stacks-edit-swarm-prune.png" alt=""><figcaption></figcaption></figure>
When you have finished making changes, click **Update the stack**.