Storage, databases, and backups

Applications that keep data need storage set up before you deploy them. You do that in Storage & Backups in the portal, not in your Git repository.

The portal shows which storage and services your account can create right now. What is available depends on your plan, your quota, and what has been enabled for you.

Add persistent storage

1. Open Storage & Backups.
2. Pick the namespace the application runs in.
3. Describe the volume you need: size, storage class, and access mode.
4. Check the quota, cost, and any warnings the portal shows you.
5. Save, and wait until the portal reports the volume as ready.
6. Reference the volume from your deployment manifests.

Creating the volume in the portal does not attach it to your application. Your manifest still has to reference it. Until it does, the volume exists but nothing uses it.

Add a managed service

Managed services such as databases are created the same way. If the portal will not let you create one, it tells you why. When the reason is that your account does not currently cover it, ask for it.

Do not work around a disabled portal action by writing the resource into Git by hand. It will not be set up correctly, and it will not be backed up.

Backups

Whether a volume is backed up, how often, and how far back you can restore depends on the storage class you chose and what your contract covers. The portal shows the protection and restore points that exist for your volumes.

Before you put production data on gh0stcloud, confirm with us in writing what your recovery expectations actually are. Do not infer them from this page. Backup scope is a contractual matter, and the answer differs between accounts.