Commit 369ac37a authored by Etienne Baqué's avatar Etienne Baqué Committed by Achilleas Pipinellis

Documentation about Pages Deployment migration

parent c23a3fa8
---
title: Add documentation about Pages deployment migration
merge_request: 59475
author:
type: added
...@@ -999,6 +999,28 @@ sudo gitlab-rake gitlab:pages:clean_migrated_zip_storage ...@@ -999,6 +999,28 @@ sudo gitlab-rake gitlab:pages:clean_migrated_zip_storage
This will not remove any data from the legacy disk storage and the GitLab Pages daemon will automatically fallback This will not remove any data from the legacy disk storage and the GitLab Pages daemon will automatically fallback
to using that. to using that.
### Migrate Pages deployments to object storage
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/325285) in GitLab 13.11
Existing Pages deployments objects (which store [ZIP archives](#zip-storage)) can similarly be
migrated to [object storage](#using-object-storage), if
you've been having them stored locally.
Migrate your existing Pages deployments from local storage to object storage:
```shell
sudo gitlab-rails gitlab:pages:deployments:migrate_to_object_storage
```
### Rolling Pages deployments back to local storage
After the migration to object storage is performed, you can choose to revert your Pages deployments back to local storage:
```shell
sudo gitlab-rails gitlab:pages:deployments:migrate_to_local
```
## Backup ## Backup
GitLab Pages are part of the [regular backup](../../raketasks/backup_restore.md), so there is no separate backup to configure. GitLab Pages are part of the [regular backup](../../raketasks/backup_restore.md), so there is no separate backup to configure.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment