search

cue-labs / oci

Go modules related to OCI (Open Container Initiative) registries
Apache License 2.0
24 stars 4 forks source link

Planning and design? #9

Closed vsoch closed 10 months ago

vsoch commented 1 year ago

Heyo! 👋 I was looking for something like this - basically an SDK in go to add endpoints to an application. It looks like you’ve recently moved it over and are making a lot of changes. I was wondering if you could share your plan and if/when this would be ready for use? Are the basic endpoints done and you are adding bells and whistles?

myitcv commented 1 year ago

cc @rogpeppe

rogpeppe commented 1 year ago

@vsoch

Thanks for your interest! It's early days yet, so I wouldn't say the API is set in stone yet, but I think it's getting there. The plan is to make ociregistry into a very stable and dependency-light module that can be used in a flexible way in projects that might require serving or using an OCI registry.

The basic endpoints are done (it does work as a real registry server) but there are still some aspects to address.

Other modules in this repository might have larger dependency requirements and/or less stability, but will still focus on the OCI ecosystem (hence the oci name of the repo).

I was looking for something like this - basically an SDK in go to add endpoints to an application.

To clarify, this repository is specifically about OCI registries, and isn't about adding arbitrary endpoints to an application, although the ociserver API exports an http.Handler implementation that can be used to mix it with other custom endpoints if needed.

As for specific plans, I am trying to create issues whenever I see something that needs doing, tagged with an "enhancement" label. If you see something that seems like a good idea, or something you think might be a problem, please feel free to raise another issue.

rogpeppe commented 10 months ago

Most of the plan is now complete, so I'm going to close this issue for now.