geOrchestra overlay details

[Gaetanbrl]

Description

It would be usefull to identify the special georchestra's features that overlay basic mapstore2 project.

Some examples :

• dedicated plugins
• authentication items or bridge to works with mapstore2
• header
• theme
• ?

I invite the community to add their knowledge to this issue via comments.

The final objective is to create a doc / have a trace (and why not a guide to be able to upgrade Mapstore2 submodule freely).

[Gaetanbrl]

Some links :

• Mapstore2 project doc : https://docs.mapstore.geosolutionsgroup.com/en/v2024.01.02/developer-guide/project-creation-script/#update-mapstore2-version-in-a-project

• old GeoSolution doc (updated ?) https://docs.georchestra.geo-solutions.it/en/latest/developer/integration/index.html#security-integration

[Gaetanbrl]

Some customization was located in /js directory (e.g plugins) :

https://github.com/georchestra/mapstore2-georchestra/tree/master/js

[Gaetanbrl]

Here, a custom configuration to insert / use easyTheming plugin (not exists in nativ mapstore2) :

https://github.com/georchestra/mapstore2-georchestra/commit/6ba8f3beca40b609eed3ed3849c68a302509a871

[Gaetanbrl]

@f-necas what about custom docker (or other build stuff) config / files / build ?

[f-necas]

@f-necas what about custom docker (or other build stuff) config / files / build ?

We override server.xml but there's a PR upstream for that, as far as I know, not a lot of customization around docker .

[Gaetanbrl]

• About authent / Login, a plugins seems bridge georchestra authent <-> mapstore authent system :

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/Login.jsx

• About usersession management, same in /js directory

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/UserSession.jsx

• About mapping header with mapstore

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/Header.jsx

• Not allowed plugin (i don't really know what's this)

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/NotAllowed.jsx

• A component to show versions (maptore2-georchestra and submodule)

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/Version.jsx

• A plugin to ease default mapstore2 theme customization without any build action

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/EasyTheming.jsx

(see this commit to understand)

• Usersession plugin that override of the standard UserSession plugin to get more informations

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/plugins/UserSession.jsx#L12 https://github.com/georchestra/mapstore2-georchestra/blob/master/js/epics/usersession.js#L67

[landryb]

the auth via sec-* headers is configured here: https://github.com/georchestra/mapstore2-georchestra/blob/master/web/src/main/resources/geostore-spring-security.xml#L55

[Gaetanbrl]

mapstore-georchestra use some Custom pages :

https://github.com/georchestra/mapstore2-georchestra/tree/master/js/pages

2 pages exists in mapstore2-georchestra :

• Admin
• ContextCreator

I need to understand correctly what this pages do.

[Gaetanbrl]

Ok pages are used by application router (e.g mapstore/#/admin):

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/app.jsx#L25 https://github.com/georchestra/mapstore2-georchestra/blob/8a3b8a13aa68c1bafee4d89aad48abe897dc4c38/js/app.jsx#L99-L101

[landryb]

it's probably specific to georchestra, because a default mapstore has the context manager on /#/context-manager ?

[Gaetanbrl]

@landryb /admin page was added from https://github.com/georchestra/mapstore2-georchestra/issues/37

[catmorales]

I don't see if you spoke about the use of SP headers

[catmorales]

Sorry I saw in https://github.com/georchestra/mapstore2-georchestra/issues/713#issuecomment-2262542262

[Gaetanbrl]

it's probably specific to georchestra, because a default mapstore has the context manager on /#/context-manager ?

This is correct @landryb.

After some tests to reproduce /admin page in mapstore2, and as I understand it, this is how it seems works.

• Create a custom page

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/pages/Admin.jsx

• Config mapstore router to user this custom /admin page from Admin component

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/app.jsx#L99-L101

• Config this page from plugin's configs/localConfig.json section

https://github.com/georchestra/mapstore2-georchestra/blob/master/js/app.jsx#L99-L101

This config will specify the /admin page content. The default geOrchestra's localConfig.json file specify to use Header, omnibar, Loginand context-manager inside.

Note that localConfig doesn't content ContextManager plugin (replace by Admin I guess). Note that ContextManager is maybe (not sur) override by custom ContextCreator page.

[catmorales]

Note that localConfig doesn't content ContextManager plugin (replace by Admin I guess).

But it's the aim of https://github.com/georchestra/mapstore2-georchestra/blob/master/configs/pluginsConfig.json

[Gaetanbrl]

About Project and mapstore2 submodule update / migration : https://training.mapstore.geosolutionsgroup.com/project/introduction/index.html#mapstore2-submodule-update

[Gaetanbrl]

In best practice part :

The list above shows the most common checks but based on the complexity of the project customization we could have additional files to compare

We maybe needs some additional infos about these additional files to compare.