Dspace BE not reading local.cfg

[Poulter, Dale]

Good afternoon,

 

Any reason for the Dspace BE (rest api) interface to not read the local.cfg file?    In the properties both at https://dev-BEinternal.edu/server/#/server/api  I get

 

 

  "dspaceUI": http://localhost:4000,

  "dspaceName": "DSpace at My University",

  "dspaceServer": http://localhost:8080/server,

  "dspaceVersion": "DSpace 7.6",

 

However, in the local.cfg I have this

 

 

# DSpace base host URL.  Include port number etc.

dspace.baseUrl = https://dev-internal.edu

dspace.ui.url = https://dev-internal.edu

dspace.server.url = https://dev-BEinternal.edu/serveri  I get

 

 

# Name of the site

dspace.name = DEVELOPMENT  VUIR

dspace.shortname = VUIR-DEV

 

 

-Dale

 

Dale Poulter Director, Library Technology and Digital Services Vanderbilt Libraries | Vanderbilt University 615-343-5388 | dale.p...@Vanderbilt.Edu | https://www.library.vanderbilt.edu Pronouns: he/him/his   My working day may not be your working day. Please do not feel obliged to reply to this email outside of your normal working hours.

 

 

[Eike Martin Löhden]

Good Morning Dale,

I don't know, if this is the case, but the settings might be overwritten by environment variables. This could happen for example, if you us a docker setting and the default docker-compose.yml from DSpace.

Kind regards,
Eike.

Am 28.08.23 um 22:03 schrieb 'Poulter, Dale' via DSpace Technical Support:

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/BN0PR08MB7470B409C8A73DDEFC148215FEE0A%40BN0PR08MB7470.namprd08.prod.outlook.com.

[DSpace Technical Support]

Hi Dale,

I've never heard of this myself.  I'd recommend verifying your local.cfg file is in the [dspace]/config/local.cfg location (where [dspace] is the location where DSpace backend is installed).

My best guess is either you are updating the wrong local.cfg (maybe one in the source code?).  Or somehow the local.cfg got moved to the wrong directory or has odd permissions on it?

It also is worth noting that some configurations are *cached* and will not reload until you restart Tomcat.  So, it's always possible that you simply need to restart Tomcat.

Tim