Skip to content

Tag: how-to

Showing page 10 of 19

Validate a SQL database file

The vip import validate-sql VIP-CLI command should be run against a SQL database file—and all reported errors resolved—before importing the file to a VIP Platform environment.

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.

Media Backups

A backup copy of all media files that are associated with a WordPress environment can be downloaded from within the application view of the VIP Dashboard.

XML-RPC Authentication

XML-RPC allows requests formatted in XML to be sent between WordPress and other systems. The XML-RPC endpoint is enabled on new WordPress sites by default since the release of WordPress version 3.5. The XML-RPC endpoint is extremely useful, but is also a common attack vector for WordPress sites. Security reviews for WordPress sites often recommend disabling the XML-RPC endpoint entirely.

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.