how-to Archives · Page 7 of 16 · WordPress VIP Documentation

Update a local environment to load application code

The VIP Local Development Environment is designed specifically for code development and testing for a VIP Platform application. A VIP Local Development Environment can be configured to run with a local git clone of an application’s wpcomvip GitHub repository. A local environment running with application code will respond to updates made to the local code without restarting, including code changes resulting from branch switching initiated by a git command.

Validate a SQL database file

The vip import validate-sql VIP-CLI command scans the format of a SQL database file for errors and potential incompatibilities with VIP Platform databases. The scan does not validate if the SQL will execute successfully after import.

Set up a third-party local development app

VIP recommends setting up a local development environment with the VIP Local Development Environment feature built into VIP-CLI. The steps outlined here are a separate and alternative method for setting up a local environment for applications such as Chassis or @wordpress/env.

Remove a user

Remove a user’s access to an organization’s VIP Dashboard and their ability to interact with an organization’s applications.

Edit user roles

Edit a user’s access permissions by updating the Org roles or App roles assigned to them. A user’s Org role and App role define the permissions they have to interact with an organization’s applications.

Invite new users

Invite new users to have access to an organization’s VIP Dashboard, and assign Org roles and App roles to them that will define the permissions they have to interact with an organization’s applications.

Debug a Node.js application

Debugging against a remote environment, such as a VIP Platform environment, can be limiting and challenging. For this reason, it is recommended to debug Node.js application issues on a local development environment. Make an effort to reproduce issues locally, and to keep the local development environment in close synchronization with remote environments.

HTTP Strict-Transport-Security (HSTS)

The VIP Platform supports and strongly encourages the use of the HTTP Strict-Transport-Security response header (HSTS). This header informs browsers that a site should only be accessed using HTTPS , and that any future attempts to access the site using HTTP will automatically be converted to HTTPS.

Media Backups

Media files associated with a WordPress environment can be viewed and downloaded in the application view of the VIP Dashboard.

Update an environment’s deploying branch

Environments with Default Deployment enabled are configured to track a specific branch of an application’s wpcomvip GitHub repository. For example, new production environments are set up to track a branch named production by default. Pushing any changes to this branch (via a push, merge, or rebase) triggers an automatic deployment to the production environment.

Tag: how-to