Hosting V4 on Webscale Product Documentation

Components

Mon, 01 Jan 0001 00:00:00 +0000

Data volume

To ensure data durability and architectural flexibility, all application file data in the V4 platform is allocated separately from the compute layer and stored on an independent, persistent cloud data volume.

Because this data volume exists independently of the core server instance, the compute layer can be destroyed, upgraded, or reconfigured without any risk to the underlying data.

In single-server configurations, this volume acts as the local storage for the application’s stateful files. As you scale to multi-server tiers (Standard, Pro, HA Pro), this same volume serves as a centralized file database, exported via an NFS shared filesystem to feed the horizontally autoscaling web nodes.

Access

Mon, 01 Jan 0001 00:00:00 +0000

Whether you are a system administrator making configuration changes, an engineer actively debugging a node, or maintaining a CI/CD pipeline deploying code, the V4 platform provides secure, role-specific pathways for accessing your servers and the Webscale Control Plane.

Interactive User Access

For direct shell access to a target server, utilize either SSH Connect or the SSH Gateway .

When you authenticate and drop into a shell, your user session is automatically assigned to the dev group. Membership in this group grants access to run commands to maintain the environment and to update files in the /var/www directory.

Deployments

Mon, 01 Jan 0001 00:00:00 +0000

The method of deploying code depends on the stack tier used.

Essentials

Code is deployed directly to the server in the /shadow/www directory.

All others

CodeDirect is used to build and deploy a container image to a cluster. Builders can be configured to deploy code automatically on completion of a successful build, triggered externally using the Webscale API , or launched using the Webscale Control Panel.