Possible conflicting localConfig.json files - what is the effect on development?
Zachary Smith
Hi Mauro,
Thank you for the advice previously (on using the standard project rather than the custom project). I'm got to the point where I'm trying to figure out how to customise the configuration files to use my own data, and customise plugins to what I need hopefully.
I see in app.jsx that there is instructions in this regard. One of the config files is "localConfig.json". What does this file do? From the contents it looks like it's the place that I can configure whitelisted CORS addresses as well as the endpoints to find data. Is this correct? I see a 'catalog' key, that includes URIs to WMS-serving servers.
I tried moving this file to the root of my generated project (standard), and then I deleted the original file to make sure that I was only loading one configuration. But it seems like this is not the case. The same file is loaded here: https://github.com/geosolutions-it/MapStore2/blob/master/web/client/jsapi/MapStore2.js
I see that this issue has been logged as high priority - https://github.com/geosolutions-it/MapStore2/issues/3688.
What is the effect on using the application while this is unresolved?
Best regards,
Zach
Zachary Smith
You received this message because you are subscribed to the Google Groups "mapstore-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mapstore-develo...@googlegroups.com.
To post to this group, send email to mapstore-...@googlegroups.com.
Visit this group at https://groups.google.com/group/mapstore-developers.
To view this discussion on the web, visit https://groups.google.com/d/msgid/mapstore-developers/872b6e1d-306c-411f-af2c-9a432bb3ea9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.