What Does \u201cRedeploy a Container\u201d Mean?<\/h2>\n
Imagine your container is a box running your app. When you redeploy, you\u2019re replacing that box with a fresh, updated one<\/b>, maybe with bug fixes or new features, without touching the stuff you want to keep<\/b> (like uploaded files, databases, or logs).<\/p>\n
What Happens Behind the Scenes?<\/b><\/p>\n
When you redeploy on Accuweb.Cloud:<\/p>\n
1. A new container<\/b> is created using the updated template or version.<\/p>\n
2. Your important data paths (volumes)<\/b> are identified.<\/p>\n
3. The old container is stopped<\/b>, and its system files are replaced with files from the new version.<\/p>\n
4. Your volume data is kept safe<\/b>, as long as the \u201cKeep volumes data\u201d<\/b> option is checked.<\/p>\n
In short:<\/b> your app gets updated, and your precious data stays exactly where it was.<\/i><\/p>\n
Step-by-Step: Redeploy via the Dashboard (Without Losing Volume Data)<\/b><\/p>\n
You\u2019ll need access to your environment via the Accuweb.Cloud dashboard.<\/p>\n
1. Open Your Environment<\/h3>\n\n- Log in to the dashboard.<\/li>\n
- Navigate to your environment (where your app is running).
![\"Open](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2025\/07\/image3.png\" "\\"Open")
<\/a><\/li>\n<\/ul>\n<\/div>\n\t\t\n\t\t\t \n \n \n \n \n \n \t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t <\/div>\n <\/div>\n <\/div>\n <\/section>\n \t\t<\/div>\n\t\t\n<\/div>\n2. Trigger Redeploy<\/h3>\n
You\u2019ve got two options to start the redeploy:<\/p>\n
\n- Click the “Redeploy Container(s)” button<\/b> next to your container or layer.
![\"Redeploy](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2025\/07\/image7.png\" "\\"Redeploy")
<\/a><\/li>\n- Or<\/b>, click the pencil icon next to the container version in the Topology Wizard<\/b>.
![\"Topology](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2025\/07\/image8.png\" "\\"Topology")
<\/a><\/li>\n<\/ul>\nBoth ways will open the “Redeploy Containers”<\/b> dialog box.<\/p>\n3. Choose the New Tag (Version)<\/h3>\n\n- In the dialog, select the new Tag<\/b> (select the desired tag corresponding to the container image version you want to deploy).<\/li>\n
- Example: 2.4.64-php-8.4.10-almalinux-9 \u2192 2.4.64-php-8.3.23-almalinux-9.
![\"Choose](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2025\/07\/image5.png\" "\\"Choose")
<\/a><\/li>\n<\/ul>\n4. Enable \u201cKeep Volumes Data\u201d (Important)<\/h3>\n
This step is critical to prevent any data loss during the redeployment process.<\/p>\n
Make sure to check the box labeled \u201cKeep volumes data\u201d<\/b> before proceeding.<\/p>\n
![\"Keep](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2025\/07\/image13.png\" "\\"Keep")
<\/a><\/p>\nThis option ensures that important data, such as database contents or user-uploaded files, is preserved. These files are stored in data volumes<\/b> that are mounted inside your container.<\/p>\n
You can view these volumes under the Volumes<\/b> tab. This tab lists the paths where data volumes are mounted within the container. These volumes are intended to retain data across container restarts or replacements, allowing the data to persist independently of the container’s lifecycle.<\/p>\n
![\"Volumes](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2025\/07\/image12.png\" "\\"Volumes")
<\/a><\/p>\nIf this option is not selected, all data stored in these volumes will be erased<\/b> during redeployment.<\/p>\n5. Click Redeploy<\/h3>\n\n- Hit the Redeploy<\/b> button.<\/li>\n
- Confirm in the popup.
![\"Redeploy](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2025\/07\/image9.png\" "\\"Redeploy")
<\/a><\/li>\n<\/ul>\nThat\u2019s it! The platform will handle the redeployment process automatically from this point onward.<\/p>\n
<\/a><\/li>\n<\/ul>\n2. Trigger Redeploy<\/h3>\n
You\u2019ve got two options to start the redeploy:<\/p>\n
- \n
- Click the “Redeploy Container(s)” button<\/b> next to your container or layer.<\/a><\/li>\n
- Or<\/b>, click the pencil icon next to the container version in the Topology Wizard<\/b>.
<\/a><\/li>\n<\/ul>\nBoth ways will open the “Redeploy Containers”<\/b> dialog box.<\/p>\n
3. Choose the New Tag (Version)<\/h3>\n
- \n
- In the dialog, select the new Tag<\/b> (select the desired tag corresponding to the container image version you want to deploy).<\/li>\n
- Example: 2.4.64-php-8.4.10-almalinux-9 \u2192 2.4.64-php-8.3.23-almalinux-9.
<\/a><\/li>\n<\/ul>\n4. Enable \u201cKeep Volumes Data\u201d (Important)<\/h3>\n
This step is critical to prevent any data loss during the redeployment process.<\/p>\n
Make sure to check the box labeled \u201cKeep volumes data\u201d<\/b> before proceeding.<\/p>\n
<\/a><\/p>\nThis option ensures that important data, such as database contents or user-uploaded files, is preserved. These files are stored in data volumes<\/b> that are mounted inside your container.<\/p>\n
You can view these volumes under the Volumes<\/b> tab. This tab lists the paths where data volumes are mounted within the container. These volumes are intended to retain data across container restarts or replacements, allowing the data to persist independently of the container’s lifecycle.<\/p>\n
<\/a><\/p>\nIf this option is not selected, all data stored in these volumes will be erased<\/b> during redeployment.<\/p>\n
5. Click Redeploy<\/h3>\n
- \n
- Hit the Redeploy<\/b> button.<\/li>\n
- Confirm in the popup.
<\/a><\/li>\n<\/ul>\nThat\u2019s it! The platform will handle the redeployment process automatically from this point onward.<\/p>\n
- Confirm in the popup.
- Example: 2.4.64-php-8.4.10-almalinux-9 \u2192 2.4.64-php-8.3.23-almalinux-9.
- Or<\/b>, click the pencil icon next to the container version in the Topology Wizard<\/b>.