We are moving to deploy the same image for worker(s) and API built with s2i from the Pebbles repo and published at oso-pilot.
Switch to using that as dependency for now.
Also, @tourunen has a dockerfile for frontend that we want to build and publish as an image as well.
ToDo: does depending on oso(-pilot) affect our SLA or availability promises? If it does how easy is it to deploy a self-built image from the deploying machine?
We are moving to deploy the same image for worker(s) and API built with s2i from the Pebbles repo and published at oso-pilot.
Switch to using that as dependency for now.
Also, @tourunen has a dockerfile for frontend that we want to build and publish as an image as well.
ToDo: does depending on oso(-pilot) affect our SLA or availability promises? If it does how easy is it to deploy a self-built image from the deploying machine?