Can I have different context path for development and production instances of confluence?

[michael_giroux]

I'm preparing to stage an update of Confluence.   We will copy the existing confluence-data and oracle database to a dev box, and perform the upgrade in development instance.  If successful, we will perform the upgrade in production.

There is no context path for our production server, but the dev box is running other apps so we need to configure context path as described in https://confluence.atlassian.com/conf67/configuring-the-server-base-url-945103616.html to allow the apache httpd proxy to route messages to the dev confluence instance.

It seems that this should work, but I wanted to confirm that I'm not overlooking something. Beyond the change to server.xml and the Server Base URL described in the reference link, is there anything else I need to be aware of?

[Nic Brough -Adaptavist- · Accepted solution]

No, you're not missing anything.  Add the context path to server.xml and change the base url in the development system, and you're done