Closed stefandesu closed 7 months ago
I just fixed building older Cocoda versions[^1].
For this particular issue, I would suggest a separate Docker image that does the following:
Then we could set the path for this container as /cocoda/*/
and have one container serve all Cocoda versions. 👍
[^1]: There were two main issues: 1) Older Cocoda versions weren't able to be built with newer Node.js versions. 2) Some older Cocoda versions were refusing to access JSKOS APIs v2+, even though it is pretty much backwards compatible. These were fixed with workarounds, some of which could be a bit more elegant...
I implemented this in https://github.com/gbv/cocoda-versions. I will test this tomorrow and switch over all our Cocoda instances if it works well.
(Closing this issue as soon as I have added it as a service here.)
Cocoda instances are now running on the new server. 👍
Currently, we are serving multiple Cocoda instances (e.g. app and dev), as well as ALL older versions of Cocoda (even if they might not work anymore): https://coli-conc.gbv.de/cocoda/
I'm not sure how to best manage and serve these in the new system. It might make sense to create a new Docker image that does only this. 🤔