We recently added the ability to take RAMP for a test drive before you buy. On the RAMP page, click that “Demo” button to sign up and we’ll set up both a staging and production WordPress site for you – with RAMP installed and configured on both sites. You can log in, create and upload content, etc. Use the Quick Send feature to send a single change over immediately or make a bunch of change, add them to a batch, and send them all at once.
RAMP is a commercial GPL WordPress plugin for migrating content between your staging server and your production server. Maybe you need to create a few new pages, update a few others, stage it for internal review and critique and then push it all live at once. Maybe you need to tweak a few existing pages and want to make sure they look right before you make the changes on your live site. This is the job RAMP does. It’s a pretty hard job and RAMP does it in an elegant manner.
To answer a question I get with some regularity, I see RAMP as primarily a business tool for website maintenance and updates rather than a developer tool for moving a side from a local development environment to a production server.1 I talk about this in some depth on the ShopTalk podcast.
Give it a try and see how it works!
- There isn’t a technical limit here, it’s just the workflow I believe makes the most sense. ↩
This post is part of the project: RAMP. View the project timeline for more context on this post.
@alexkingorg Nice!
@alexkingorg You guys should probably change the font color on the RAMP demo email blurb: http://t.co/kWRNZuRB
@DrewAPicture @alexkingorg Which OS and mail client were you using in that screenshot? All my tests came through with that text in white.
That’s pretty slick 🙂 I’m thinking about using this for a project, and it’s nice to be able to actually use try it out, instead of relying on marketing materials.
A few small problems I noticed:
* I couldn’t change the local/remote settings to test a bi-directional sync. I’m guessing that’s because RAMP doesn’t support that yet? If that’s the case, maybe the interface should be designed to reflect that? Having option fields for both seems to imply that it does support two-way syncs. Maybe instead there should be a radio button at the top that says “This server is…” and the choices are “staging” and “production”. Then, the user gets only the options they can use based on the value of the radio field.
* The bottom of the settings page says I don’t have the permission to change the settings, but it still lets me view the setting page, which contains the auth token. Is that just in the demo, or would non-admins be able to see auth token in real installations? If so, that could be a security vulnerability.
* I got a memory error when using the “Test” button on the settings page. I’m guessing this is just because it’s a demo, though.
Here’s our FAQ on this: http://crowdfavorite[...]-to-staging/
You must be an admin to see these settings.
That’s likely, it’s running on a shared box with limited resources.
Sounds good, thanks 🙂