hirosystems / hirosystems/stacks-devnet-api
enable image-streaming
- Vorherrschende Sprache
- Rust
- Sterne
- 2
- Forks
- 0
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
In order to start using Image-streaming for any of the docker images we are pulling, it is necessary to update any docker image pull commands with this format:
`us-east4-docker.pkg.dev/{env_id}/{gar_repo}/{repo}/{image}:{tag}`
The available env_id and gar_repo are:
env_id:
```
dev: epd-dev-storage-c697
stg: epd-stg-storage-a312
prd: epd-prd-storage-09b4
```
gar_repo
```
hirosystems-remote
blockstack-remote
```
e.g.
```
us-east4-docker.pkg.dev/epd-dev-storage-c697/hirosystems-remote/hirosystems/platform-backend:feat-pricing-page
or
us-east4-docker.pkg.dev/epd-dev-storage-c697/blockstack-remote/blockstack/stacks-core:3.1.0.0.7
```
note: There are some image push overlaps between the two docker hub orgs so it is best the `{gar_repo}` and `{repo}` should correspond to one another
```
hirosystems-remote | hirosystems ✅
hirosyustems-remote | blockstack ❌
```
Beitragsleitfaden
Rechercherichtung
Start by locating every Docker image pull command in the repository and compare its image references with the required Artifact Registry format. Update references so the environment, registry repository, Docker organization, image, and tag correspond correctly; done means all relevant pulls use the matching image-streaming paths.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- docker
- Bereich
- devops, infrastructure
- Issue-Typ
- Feature
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 48/100