Managing deployments

Once your application is running, the Clouve dashboard is where you monitor its health, apply updates, and control its lifecycle. This page covers day-to-day operations for business users.

The deployment dashboard

The main dashboard shows the following for each deployment:

Click a deployment to open its detail view, which has more information and the available actions.

Monitoring your application

Status indicators

The platform restarts crashed containers automatically. A container that crashes repeatedly (three or more times in quick succession) shows Failed and needs investigation.

Automatic recovery

The platform monitors your application continuously with health checks. If a container stops responding:

1. Kubernetes attempts to restart the container
2. If restarts resolve the issue, the status returns to Running on its own
3. If restarts don't help after several attempts, the status changes to Failed

The platform handles most transient issues, such as temporary network glitches or brief resource spikes, without any action from you.

Applying updates

When a new version of an application is available in the marketplace, an Update Available notification appears on the deployment card.

An update may contain security patches for known vulnerabilities, bug fixes, new features, or newer versions of the underlying software. Apply security patches promptly.

How to update

1. Open the deployment detail view
2. Click Update to Version X.Y.Z
3. Review the change summary (if provided)
4. Click Confirm Update

The platform then:

1. Downloads the new application version
2. Starts new containers alongside the existing ones
3. Shifts traffic to the new containers once they're healthy
4. Removes the old containers

This sequence keeps downtime to a minimum. In most cases the application stays accessible throughout the update, though brief interruptions (typically 10 to 30 seconds) are possible during the transition.

Before updating

If you have a non-production workspace, apply the update there first to verify everything works before touching production. Schedule major updates for low-traffic periods, and for applications with many users, announce the planned update window in advance.

If an update fails

The platform rolls back to the previous version automatically and your data is preserved. Contact support with the error details.

Starting and stopping a deployment

Stopping a deployment

Stopping an application shuts down all its containers while keeping all data. Do this when the application isn't needed for a while, when you want to reduce resource usage, or when you need to perform maintenance.

From the deployment detail view, click Stop Deployment.

Important: Stopping a deployment does not delete any data. Everything stored on the persistent volumes (database records, uploaded files) is preserved, and the application can be restarted at any time.

Starting a stopped deployment

Click Start Deployment in the deployment detail view. The application goes through the same startup sequence as an initial deployment, so expect 3 to 10 minutes before it is fully available.

Deleting a deployment

Deleting a deployment permanently removes all application containers, all application data (databases, uploaded files, configuration), and the workspace's HTTPS URL assignment.

This action is irreversible. Before deleting, export any data you need to keep (download database dumps, export files, or use the application's built-in export features), confirm with your team that no one is still using the application, and make sure important data has a backup copy.

To delete a deployment, open the detail view, click Delete, type the deployment name to confirm, then click Confirm Delete.

Data export and backup

Persistent volumes protect your data against container failures. Backups are not switched on by default: on a paid plan, use the deployment's Backups tab to schedule them (daily, weekly or monthly) or take one on demand. For business-critical data, also export regularly.

How to export data

WordPress:

• Use the built-in Tools → Export to export content as XML
• Use a plugin like UpdraftPlus for full database + file backups

Moodle:

• Go to Site Administration → Server → Backup → Automated Backup to configure scheduled backups
• Manually: Site Administration → Courses → Restore

SuiteCRM:

• Admin → Studio for schema exports
• Use the import/export functionality in each module

Odoo:

• Use the Backup Database feature in Settings → Technical → Database Structure → Backup

For scheduled or on-demand backups of the whole deployment, use the Backups tab (paid plans).

Managing multiple deployments

If your organization runs several deployments (different applications, or the same application in different workspaces), the dashboard lists all of them, organized by workspace. Production and staging environments appear under their own workspace headings, and the search bar and category filters help you find a specific deployment quickly.

User access and permissions

Access to the Clouve dashboard, including who can deploy, stop, or delete applications, is controlled by your organization's Clouve account settings. The roles are:

• Organization Admin: can deploy, configure, stop, delete, and invite other users
• Member: can view deployments and access application URLs, and may have deployment rights depending on settings
• Viewer: read-only access to the dashboard

Contact your Clouve administrator to adjust user permissions within your organization.

Common management tasks

I need to change the application password

Log in to the application itself and use its built-in password change function. The platform does not provide a way to reset application-level passwords; that is handled within the application.

The application is running but slow

Performance issues usually have one of these causes:

1. Resource limits: the container may not have enough memory or CPU. Contact your administrator to increase the resource allocation.
2. Application-level issues: too many plugins, unoptimized queries, or misconfiguration inside the application. Check the application's performance settings.
3. Traffic spikes: performance may degrade when many users hit the application at once. Contact your administrator about scaling options.

I need to move the application to a different cloud region

This requires administrator involvement. Contact your Clouve administrator with the request.

The application shows an error page

1. Check the deployment status in the dashboard; the application may be restarting
2. Wait 2 to 3 minutes and try again
3. If the error persists while the status shows Running, contact support with a screenshot of the error

Next steps

• Security and compliance →: how your data is protected
• Support →: getting help with issues you can't resolve yourself