RAMP requires that certain settings are configured before it can function properly.
Each server needs to have an authentication key defined. This authentication key helps maintain proper server identification during the deploy process. If the server token is empty, use the “Generate” button next to the token field to auto generate a random token string. This can be changed at any time, but if changed any servers that are using the authentication key for verification will need to be supplied the new key before they can send batches to this server.
Production Server Settings
To send this server’s data to another server enter the production server’s url and authentication key here. Without these settings the RAMP process will not function.
If the production server is behind HTTP Authentication some modifications to the server’s
.htaccess file will be required for deploy to properly function. Modify the HTTP Authentication section of your
.htaccess file to look like the section below to enable RAMP to function properly through HTTP Authentication:
# Standard HTTP Auth AuthType Basic AuthName "My Protected Server" AuthUserFile /path/to/.htpasswd Require valid-user # additions for RAMP SetEnvIf Request_URI "(/wp-content/uploads/)" allow SetEnvIf Request_URI "(xmlrpc.php|async-upload.php|wp-cron.php)$" allow Order allow,deny Allow from env=allow Satisfy any