Re: [ALA-Portal] Purpose of generic repositories
![](https://secure.gravatar.com/avatar/b00b31d9d6eecf2d4240863dd7949e92.jpg?s=120&d=mm&r=g)
Hey Vicente,
Your advice and links are very helpful.
You'll receive in short an invitation to slack where we discuss these topics.
I have received an invitation---thank you. I will lurk in the background and catch up on previous messages.
Many LA portals use directory the ala generated artifacts
This is what I expected from my reading of the Ansible scripts; I'm just trying to get a feel for how building the system from scratch might work so we understand which pieces go where.
Is there any documentation listing the dependency graph between the repositories? I will follow this up via Slack.
Thanks,
Alex
![](https://secure.gravatar.com/avatar/3f75eced4f493be45a3810246700a623.jpg?s=120&d=mm&r=g)
El 11/10/21 a las 12:28, Alex Melbourne escribió:
Is there any documentation listing the dependency graph between the repositories? I will follow this up via Slack.
Good morning Alex,
About dependencies, it does not exits (or better I don't remember) such a module dependency graph.
The la-toolkit itself shows you with modules are optional and which are recommended, the dependencies (*) and conflicts (when you try to install together services that are not compatible).
Also maybe you'll find interesting a list of portals and modules that use: https://github.com/AtlasOfLivingAustralia/documentation/wiki/Components-vers...
And if you want something more detailed, this new page: https://github.com/AtlasOfLivingAustralia/documentation/wiki/Dependencies
(*) The code that describe these service deps is here (and is quite readable): https://github.com/living-atlases/la-toolkit/blob/3a23deb5ce42dc751d5b4c24bf...
BR,
Vicente
participants (2)
-
Alex Melbourne
-
Vicente J. Ruiz Jurado