Change to using docker images from oso-pilot registry.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
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?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Ansible deployment entries for the worker, API, and frontend images, then inspect the referenced Pebbles s2i image and @tourunen's frontend Dockerfile. Done means deployments use the oso-pilot images and the issue's SLA, availability, and self-built-image questions have documented answers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100