Comments on: JumpBox. What about upgrades? http://www.movingwalkway.net/archives/jumpbox-what-about-upgrades stand to the right, walk to the left Wed, 03 Dec 2008 23:25:38 +0000 http://wordpress.org/?v=2.6.3 By: joransen http://www.movingwalkway.net/archives/jumpbox-what-about-upgrades#comment-59 joransen Wed, 06 Jun 2007 19:00:19 +0000 http://www.movingwalkway.net/archives/jumpbox-what-about-upgrades#comment-59 Kimbro, Thanks for the comment. Shortly after posting I actually read through JumpBox's site some more and found the notion about moving the data as an upgrade mechanism. Totally makes sense, especially if things are in the database. Should work well for my first exploration around SVN and Trac. Since I run WordPress here, I'm interested in seeing how that plays out. All content is in the database, but styles, themes, plugins are in the file system. How those are handled will be interesting. If it plays out well for the "non-dramatic" upgrade/update, then this alone would justify the kind of $$$ JumpBox is asking (which looks reasonable). Every "upgrade" has three components (at least): The base system, your data, and your customizations. JumpBox solves the first, sounds like it will get the second one done well, if it hits the third in a decent way... bingo. Kimbro, Thanks for the comment.

Shortly after posting I actually read through JumpBox’s site some more and found the notion about moving the data as an upgrade mechanism. Totally makes sense, especially if things are in the database. Should work well for my first exploration around SVN and Trac.

Since I run WordPress here, I’m interested in seeing how that plays out. All content is in the database, but styles, themes, plugins are in the file system. How those are handled will be interesting. If it plays out well for the “non-dramatic” upgrade/update, then this alone would justify the kind of $$$ JumpBox is asking (which looks reasonable).

Every “upgrade” has three components (at least): The base system, your data, and your customizations. JumpBox solves the first, sounds like it will get the second one done well, if it hits the third in a decent way… bingo.

]]> By: Kimbro Staken http://www.movingwalkway.net/archives/jumpbox-what-about-upgrades#comment-58 Kimbro Staken Wed, 06 Jun 2007 17:41:28 +0000 http://www.movingwalkway.net/archives/jumpbox-what-about-upgrades#comment-58 Upgrades are handled by bringing up another instance of the VM exporting the data from one and importing it into the other. This sounds a little cumbersome, but it's actually a much more robust way of performing an upgrade because it keeps your existing system fully functional while you test the updated system. When you're confident everything is working you can cut over to the new VM while still keeping the original fully in tact in case you need to switch back. This is a big advantage of using virtualization infrastructure. Upgrades are handled by bringing up another instance of the VM exporting the data from one and importing it into the other. This sounds a little cumbersome, but it’s actually a much more robust way of performing an upgrade because it keeps your existing system fully functional while you test the updated system. When you’re confident everything is working you can cut over to the new VM while still keeping the original fully in tact in case you need to switch back. This is a big advantage of using virtualization infrastructure.

]]>