-
Notifications
You must be signed in to change notification settings - Fork 2
Components versioning
vjrj edited this page Nov 27, 2024
·
58 revisions
Do no edit this first table, is auto-generated using this other page and this script.
First of all your ansible inventories and ala-install default values should specify the module versions that should be running in your portal.
But if you want to check this in runtime, there are different ways to check it:
- Services with url many times have a
meta
field with theapp.version
on it, like:<meta name="app.version" content="1.5.0"/>
- also many services have a
/buildInfo
url that exposes versions and other software relevant info (as you can see in the above table). - Other option is to search the ALA nexus by checking the
sha1
of a war/jar, for instance:
$ sha1sum /var/lib/tomcat9/webapps-records-your-l-a.site/ROOT.war
fd18adf5b8108179d65b495f5a9af9fed3773cd4 /var/lib/tomcat9/webapps-records-your-l-a.site/ROOT.war
and https://nexus.ala.org.au/#nexus-search;checksum~fd18adf5b8108179d65b495f5a9af9fed3773cd4 shows that this is 2.5.1
or biocache-service
.
Index
- Wiki home
- Community
- Getting Started
- Support
- Portals in production
- ALA modules
- Demonstration portal
- Data management in ALA Architecture
- DataHub
- Customization
- Internationalization (i18n)
- Administration system
- Contribution to main project
- Study case