Skip to content

container-registry/npm-registry-oci

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

NPM private registry over the OCI protocol (POC)

The current project is a Proof-of-concept of using OCI as a backend for the NPM registry.

What is it good for?

Store your private NPM packages safely as artefacts in your existing OCI compliant registry infrastructure.

Usage

TBD

Example

Please check the testdata folder

Supported API methods

  • npm login with legacy auth method (any credentials)
  • npm publish
  • npm install

Environment Variables

There are not many options in configure the application except the following.

  • PORT - specifies port, default 9000
  • DEBUG - enabled debug if it's TRUE
  • USE_TLS - enabled HTTP over TLS
  • OCI_URL - OCI compliant registry e.g. oci://admin:bitnami@localhost/library

TODO

  • Add authorisation flows
  • CI/CD Pipeline with GitHub Action
  • Add tests

About

Private NPM registry with OCI compliment storage as a backend

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published