jdolitsky | 2 years ago | on: Open Container Initiative announces upcoming changes for registries
jdolitsky's comments
jdolitsky | 2 years ago | on: Open Container Initiative announces upcoming changes for registries
- Repositories in the registry are namespaced under /v2/<name>/...
- Legacy clients already support parsing OCI manifests (vs. WebFinger JSON)
jdolitsky | 2 years ago | on: Summary of Upcoming Changes in OCI Image and Distribution Specs v1.1
jdolitsky | 2 years ago | on: Open Container Initiative announces upcoming changes for registries
jdolitsky | 12 years ago | on: Node/Ember/Parse (Neptune) app w/ Facebook login
jdolitsky | 13 years ago | on: LinkedIn: The Creepiest Social Network
jdolitsky | 13 years ago | on: LinkedIn: The Creepiest Social Network
jdolitsky | 13 years ago | on: Tearable Cloth Simulation in JavaScript
jdolitsky | 13 years ago | on: Living Code. Show off your code in a fancy way.
jdolitsky | 13 years ago | on: Why I left Google (2012)
jdolitsky | 13 years ago | on: Conflicts with co-founder, nearly bankrupt, unknown future
jdolitsky | 13 years ago | on: AppDotNetPHP - PHP Library for the App.net API
jdolitsky | 13 years ago | on: Hot girl helps friend with dry erase board
jdolitsky | 13 years ago | on: Meteor 0.5.8: security fix, AppCache, DB transforms, new Deps
jdolitsky | 13 years ago | on: As of today, App.net is a freemium service
jdolitsky | 13 years ago | on: As of today, App.net is a freemium service
jdolitsky | 13 years ago | on: The best place on the web to learn anything, free.
jdolitsky | 13 years ago | on: Show HN: Like The Onion, But Real
jdolitsky | 13 years ago | on: JSDB.io - A Database of JavaScript Libraries
jdolitsky | 13 years ago | on: Announcing the App.net File API
The way to indicate a non-container artifact type is to use the "artifactType" field. Your client may choose whether or not to support older <=v1.0 registries by falling back to use "config.mediaType". The way to attach the artifact to the image is to use the "subject" field, pointing "subject.digest" to the proper digest of the thing you're pointing to (e.g. "sha256:..." ). There are no limitations there either, you may point cat pictures to cat pictures.