Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Upgrading Roxy

Jump to bottom
dmcassel edited this page Nov 9, 2012 · 11 revisions

We continue to make improvements to Roxy. Every now and then, you may want to upgrade an existing Roxy-based project to the latest version of Roxy. This page is not intended to get you from any version of Roxy to any later version of Roxy, but should cover most cases.

Copy files

Assuming that I have

~/git/old-app/
~/git/roxy/

and both are up-to-date and have no local modifications.

$ cd ~/git/old-app/
$ cp -r ~/git/roxy/deploy/* deploy
$ cp -r ~/git/roxy/src/roxy/* src/roxy
$ cp ~/git/roxy/ml .
$ cp ~/git/roxy/ml.bat .

The deploy and src/roxy directories are Roxy code. Your source code modifications should not have touched anything under src/roxy. Your only changes under deploy should be ml-config.xml, build.properties, and {environment}.properties files, none of which will exist under Roxy's deploy directory.

Re-bootstrap

You'll want to make sure that your updated code and configuration work completely. You can test by doing the following steps (I'm using the local environment to test):

# THIS WILL FULLY REMOVE YOUR APP FROM MARKLOGIC, SOURCE AND DATA
$ ml local wipe
$ ml local bootstrap

If the bootstrap doesn't result in the full setup that you expect, try it with the verbose flag:

$ ml local bootstrap -v

Once that works, deploy your modules and content and test your app.

Troubleshooting

  • Verify that your configuration files didn't get stomped.
  • The old version of the app might not have had the src/roxy/config/defaults.xqy, which is where some of the default configuration is now set up. Compare ~/git/roxy/src/app/config/config.xqy to your src/app/config/config.xqy. If your old version is old enough, you may need to manually revise your config.xqy to be like what's now distributed.
Clone this wiki locally