Get started with App Storage
App Storage adds persistent space to supported Cloud Apps in Dallas. You buy a pool, divide it into volumes, then attach each volume to an app's listed storage path. Several apps can share the pool's capacity, while each volume has its own assignment.
App Storage is currently a private preview with ordering restricted to administrators. These instructions describe the available preview controls; if you cannot see them, contact support about access.
What does App Storage replace?β
An attachment replaces the storage backing one selected persistent-volume path. The app keeps using the same folder, but reads and writes at that path go to the storage server instead of the app host's local volume.
For example, attaching a website's files does not also move its database or configuration. Those are separate paths and need their own supported attachments. The app itself still runs on its Cloud App host.
The panel copies the existing local files to the new volume during attachment. The original local volume remains, but it is not kept in sync. Attaching does not combine the two volumes into one larger filesystem or automatically free the old local copy's disk space.
Read how attachment changes the data path, especially before detaching: detaching returns the app to that older local copy without copying newer data back.
Create a poolβ
- Open Storage β App Storage.
- Under Choose your App Storage, enter a pool name and select Dallas.
- Choose the capacity. The minimum is 100 GB at $0.60/month, in 100 GB increments. The current private limit is 500 GB per pool.
- Select Review storage, check the price and terms, then Create invoice.
- Pay the invoice. Return to the pool and wait for its billing status to show Active.
Allocate a volumeβ
In the pool, enter a Volume name and Size (GB), then select Allocate volume. The size comes out of the pool's available capacity. Wait for the volume to finish provisioning and show Allocated / not attached.
For example, a 100 GB pool could contain a 20 GB website volume and a 30 GB media volume, leaving 50 GB unallocated. Allocating capacity is not the same as filling it with files. Filesystem formatting also consumes some space inside a volume.
Attach itβ
Stop the destination app first. The Attach to a stopped app list shows the app, service and path that are eligible. Choose the correct entry and select Attach storage. Follow Attach storage and find your files before restarting the app.
Keep the two products separateβ
Backup Storage is a standalone SSH-key account for transfer tools. App Storage is mounted into a Cloud App and uses that app's Files page for file access. You do not receive a second Backup Storage login when you create an App Storage pool.