Reorganizing georchestra codebase

[Florian Necas]

Hi geOrchestra team !

Hope you all doing well :)
I wanted to talk with you about a wish for geOrchestra codebase. 

I've created a moment ago, a diagram with geOrchestra apps, separating what we can call "core apps" (auth/database/ldap...) than "module apps". It's quite a subjective/dev oriented choice. 

Here is the diagram :


In georchestra/georchestra repo we will have only core/essentials modules except Cas, gateway, security proxy. (Seems it doesn't get a lot of things inside but there's a lot, like common components, ldap, database).

If we do that, we will remove analytics, datafeeder, geonetwork, geoserver, og cserver statistics, testcontainers and security-proxy in separate repos. 

I think it can help developers to maintain smaller components and ease upgrade/maintainability of each one and even upgrading a single component.

Downside, we must maintain version in every app, but with a tool like Renovate, I think we can automate this.

What do you think ? This will be done gradually starting with datafeeder.

BTW, I wanted to propose to the geonetwork community to drop datafeeder in geonetwork-ui and create a repo for it in georchestra organisation, as it is mostly a georchestra module. 

Thanks for reading and have a good evening,
Florian 

[Landry Breuil]

On 06/03/2025 17:44, Florian Necas wrote:
> Hi geOrchestra team !
>
> Hope you all doing well :)
> I wanted to talk with you about a wish for geOrchestra codebase.
>
> I've created a moment ago, a diagram with geOrchestra apps, separating
> what we can call "core apps" (auth/database/ldap...) than "module apps".
> It's quite a subjective/dev oriented choice.
>
> Here is the diagram :

> geOrchestra-full-c2c.jpg
>
> In georchestra/georchestra repo we will have only core/essentials
> modules except Cas, gateway, security proxy. (Seems it doesn't get a lot
> of things inside but there's a lot, like common components, ldap, database).
>
> If we do that, we will remove analytics, datafeeder, geonetwork,
> geoserver, og cserver statistics, testcontainers and security-proxy in
> separate repos.
>
> I think it can help developers to maintain smaller components and ease
> upgrade/maintainability of each one and even upgrading a single component.

i get where you're coming from, since apparently for docker concerns
it's a pain to make a 'full' release. or there's another motivation ?

the main concern i have with splitting everything in separate repos (as
i've repeatedly said everytime this topic was brought), is that i fear
it will just complicate the build process.

right now, in the georchestra repo with the current git submodule scheme
for GS/GN, the Makefile allows to build 'everything' (that is in the
monolitic repo) in a single command (and that's how the buildbot/CI does).

having a dozen of repos will just put a bit more work on people building
from the source (which i guess is.. not that many people. maybe only me)
- it might also make inter-dependencies between modules versions for
building complicated ?

as long as it's properly documented..

also, what is this 'apache nas' advanced viewer ? :)

--
Landry Breuil

[Florian Necas]

Hi Landry, 

Thanks for your answer. It isn't from a docker point of view but mainly for bumping version and keeping security updates. 

It was a pain to bump spring boot to version 2 for the whole georchestra project, and I suppose if, by example, datafeeder is out of main project it would be easier to do it on a single repo without interfering with others.

If we move to separate repo's, I'll try to make it as simple as possible.

Apache nas advance viewer, well, isn't a viewer. It's an apache server used at Camptocamp to serve static files.

--
--
projet: http://www.georchestra.org/

---
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes georchestra-dev.
Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse georchestra-d...@googlegroups.com.
Pour afficher cette discussion, accédez à https://groups.google.com/d/msgid/georchestra-dev/36c68bed-787e-4557-9bc3-bd0535fc8c37%40craig.fr.