tell production server to look for modules in secondary location?

LabKey Support Forum (Inactive)
tell production server to look for modules in secondary location? Ben Bimber  2015-10-16 09:18
Status: Closed
 
On one of our production servers, we are now including a module not part of our core distribution. when i do the normal manual-install.sh script, this blows away labkey/modules, meaning my custom module is also gone. i thought there was some way to tell the server to also check in a secondary location, like labkey/customModules, where I could drop my additional modules and they would remain even if I update my core code. I tried /extraModules and /customModules on the hope there was a default setting. Do I need to add something to ROOT.xml/labkey.xml?

Thanks.
 
 
jeckels responded:  2015-10-16 09:24
By default, the server will look in ./externalModules as well as ./modules:

https://www.labkey.org/wiki/home/Documentation/page.view?name=moduleUpgrades

You can override this to point at a different location using the -Dlabkey.externalModulesDir system property on the command-line for starting up the Tomcat VM.

Thanks,
Josh
 
Ben Bimber responded:  2015-10-16 09:29
that's it. just couldnt remember the name. thanks.