Jump to content

RAMP

RAMP

Painless Data Migration From Staging to Live WordPress Sites

Demo

Experience RAMP for yourself on our demo server.

Used RAMP on a few clients myself, it is great for content. Kudos to @alexkingorg and @crowdfavorite for the plugin

— Rachel Baker, @rachelbaker

RAMP makes it easy to start publishing in an efficient and professional way.

— Sarah Gooding, WPMU

Ch-ch-ch-changes

RAMP allows you to make all the changes you need in your staging environment, then selectively push these changes to your production site. You can set up a new section of your site, upload some images to fill out a nice carousel for it, and add a link to it on your home page. Once this content has been reviewed and approved, you can go to your RAMP page, select these content changes, and push them to your production site.

Be Selective

When pushing content with RAMP, you have the ability to choose exactly what is included. If you’re working on changes to two different parts of your site, you might want to push one set of changes while you continue to work on the other. No problem, RAMP gives you the option to select just the changes you want to push – including a handy date tool to let you see only changes newer than a certain date.

ramp-create-modify
ramp-preflight

Measure Twice, Cut Once

Changes all set and ready to go? Excellent! Before we push them up to production RAMP will run a special pre-flight check that will make sure that everything will go smoothly. The pre-flight check is also a great way to double-check what you’re planning to push.

Preflight Checklist

  • Categories, tags and users that are referenced by other posts, pages, etc. will be created automatically in production.

  • When a child page is included on a batch without the parent page, and the parent page doesn’t exist in production.

  • A selected child category where the parent category is not in production and isn’t part of the batch.

  • If an image is selected to be included in a batch, but the image was deleted from the file system (outside of WordPress).

  • If a page, category or tag is included in a selected menu, but doesn’t exist in production and isn’t part of batch.

  • Content that has changed on production and is newer than the changes on staging.

Advanced Whoops Protection

RAMP integrates with (and extends!) the built-in WordPress revision system. This means that all of your post and page changes are stored in WordPress for easy, granular roll-backs, and we also store revisions of your custom fields as an added bonus. For other items you can include in a batch, we store a before and after state so that we can put things back as they were.

One Click Rollback

Ever have that feeling of dread after hitting a button? No, no NO!!! I didn’t mean to do that, ACK! It happens to all of us, luckily RAMP includes an Oops! button. If you need to “undo” a batch, you can simply log into the production server and click the “roll back” button for the latest batch.

ramp-rollback

Supports all WordPress Content

RAMP supports not only standard posts and pages, but also custom post types and taxonomies. We also utilize the built-in XMLRPC interface for site to site communication.

Revision System Integration

RAMP fully utilizes the built-in WordPress post/page revision system. For content that isn’t included in the built-in system, we create and store our own revision data. This way we can make sure that rollbacks are painless.

Simple Installation

  1. Install the plugin on both your staging and production sites.
  2. Generate an authorization key on your production site.
  3. Add the URL and authorization key from your production site on your staging site.
  4. Create a batch and send!

Extensible System

The framework for RAMP is fully extensible using the standard WordPress hook and filter system. This means any plugin or feature can choose to make data available to RAMP. Our own Carrington Build functionality is fully RAMP-enabled.

Limitations

The following items are currently unsupported:

  • Code deployment (theme and plugin file changes)
  • Two-way data synchronization between staging and production
  • Comments
  • Unattached images/media
  • Settings (core and plugin settings, unless they opt-in to RAMP)
  • Self-signed SSL certificates (between servers)

Supported Data Types

  • Posts
  • Pages
  • Custom Post Types
  • Categories
  • Tags
  • Custom Taxonomies
  • Users
  • Links
  • Menus
  • Attachments

Requirements

  • PHP 5.2.4+
  • Dev and prod servers must be accessible to each other
  • WordPress 3.3+
  • XMLRPC must be enabled

RAMP Customers: Please review the documentation and join us in the forums if you have any questions.