Configuring eXist/Jetty for single app deployment
As we move towards deploying standalone eXist/Jetty applications for our projects, we're figuring out how best to configure them. One issue is that we're probably going to want to point the subdomain (graves.uvic.ca
or whatever) at the /apps/graves/
subfolder, but we're still going to need access to some of the default eXist applications such as eXide and the dashboard. This can be accomplished by adding the following line to the webapp/WEB-INF/controller-config.xml
file:
<root pattern="/apps/graves/apps" path="xmldb:exist:///db/apps/"/>
Add it as the first entry before similar entries. The effect of this is to leave all the existing graves app functionality handled by the apps/graves/controller.xql
, but hand anything accessed on /apps/graves/apps
to the appropriate app controller. My testing with eXist 3 RC1 confirms that this works; it should mean that on going live, the dashboard (for instance) would be accessible on graves.uvic.ca/apps/dashboard
(and we can access it over TLS for better security when logging in).
