iStock_000003850032XSmallWe <3 developers. And we love it when developers do creative and innovative things with JumpBoxes. To encourage more of this we’ve decided to make all deployment JumpBoxes completely free. This is our treat for you this Halloween.

If you’re a developer you can use these in numerous ways to speed up your development and testing processes. Here are some tricks:

  • Isolated dev environments for multiple projects Rather than running a single set of resources on your desktop that are shared amongst many different projects, you can use a JumpBox for each and have pristine project isolation. This means less entanglement and changes you make to the app server, web server or database won’t introduce issues for other apps.
  • No surprises when it comes time to deploy in production If you build your application on a JumpBox you can deploy it to production very easily using our built-in migration mechanism. Unlike moving code between a desktop dev environment to a server in your data center, there are no surprises when moving a JumpBox into production. You know it will work identically wherever it lives.
  • Rapid proofing and staging capabilities when used in conjunction with Cloud Gear How often do you have to show your boss or your client a proof of your application while it’s still in development? If you develop on a JumpBox you can make use of Cloud Gear to quickly bring up an instance of your deployment JumpBox in the cloud and demo your app publicly. Tear it down when you’re done and pay only pennies for the time you use.
  • A convenient way to distribute apps Maybe you have an app that requires a lot of custom configuration and .ini file tap-dancing to get it working? Rather than burdening the end user with a massive readme file with a bunch of ways they can mess it up, why not package your app using the JumpBox backup system and distribute this file? This is a great way to distribute a complex app. The end user simply gets the corresponding JumpBox, injects the backup and immediately has a working version of the app with all the customizations and sample data you set up.
  • Tech support implications How do you currently support users that have trouble with your application? Whether it’s via phone, email or support forums it probably consists of a series of back and forth interaction (ie. “what do you see now” - “here’s a screenshot” - “now try this and tell me what you see”…). What if instead you could have your user just send you a copy of their exact setup and you could fix it yourself and send it back? If you’re app is built on a deployment JumpBox you can do this very thing using the backup system. It creates a delta of the changes that have been made since the original so it’s a very small file but can be merged back with a blank JumpBox to re-create what the user has.
  • An easy way to test compatibility across versions of the app server Maybe you’re planning to distribute your app traditionally and have users run it natively but you need an easy way to see how it works earlier versions of the app server or the database? You can use Cloud Gear to speed up regression testing across past versions of the deployment environment by launching historical versions of the JumpBox simultaneously and deploying your app into them.
[![](]( [![](]( [![](]( [![](]( [![](]( [![](](

There are probably many other ways deployment JumpBoxes can be used. What other creative uses can you envision?