At Greenwich, we're using ghcr.io/wearefuturegov/outpost-api-service:latest as the base image for our Outpost API, which I think you helped to set up in the first place.
Recent changes here meant that the port changed, which took us a few weeks to identify and resolve.
To mitigate this in future it would be super handy to be able to pin the docker image to a known release version .
Might it be possible to start tagging releases and building appropriately named / tagged docker images from these releases?
Hi @apricot13 and friends!
I hope you are well.
At Greenwich, we're using ghcr.io/wearefuturegov/outpost-api-service:latest as the base image for our Outpost API, which I think you helped to set up in the first place.
Recent changes here meant that the port changed, which took us a few weeks to identify and resolve.
To mitigate this in future it would be super handy to be able to pin the docker image to a known release version .
Might it be possible to start tagging releases and building appropriately named / tagged docker images from these releases?
Many thanks,
Finn