How should bartoc.org pick up new jskos-server releases?

[rodolv-commons]

I learned that a new jskos-server release is not automatically picked up by bartoc.org, and this can lead to breaking changes if bartoc.org still ships an older bundled version.

I see three possible ways forward:

1. Manual rebuild of the bartoc.org Docker image
   We can use a manual workflow button to rebuild/publish the Docker image when needed.
   I added workflow_dispatch in dev for this (only for admin users)

2. Handle it in Dockerfile
   Another option would be to release bartoc.org update jskos-server for example something along these lines:

   ARG JSKOS_SERVER_REF=v2.4.1
   RUN git clone --depth 1 --branch ${JSKOS_SERVER_REF} https://github.com/gbv/jskos-server.git  && cd jskos-server && npm ci

3. Longer-term solution
   I would prefer a cleaner separation: bartoc.org should not be responsible for setting up the jskos-server instance for the BARTOC ecosystem. In that setup, bartoc.org would only talk to something like jskos-server-bartoc, instead of bundling and managing it itself.

[nichtich]

jskos server instance of bartoc is part of bartoc.org so it is right to not update automatically. But I'm fine with option 3 so we will have three components, each updateable independently:

• bartoc.org web interface
• bartoc-search search engine
• jskos-server-bartoc database

Both bartoc.org and bartoc-search expect a mininum version of jskos server with specific configuration.