Skip to content

Instantly share code, notes, and snippets.

@marshyski

marshyski/yum-nginx-api-v1-proposal.md

Last active June 21, 2020 22:27
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save marshyski/f1d69ce007a3080139d9ea8b38477a26 to your computer and use it in GitHub Desktop.
Save marshyski/f1d69ce007a3080139d9ea8b38477a26 to your computer and use it in GitHub Desktop.
Download ZIP
yum-nginx-api 2020 v1 proposal
Raw
yum-nginx-api-v1-proposal.md

Move API routes:

Old New
/api/health /v1/health
/api/upload /v1/rpm/upload /v1/deb/upload
/api/repo /v1/rpm/repo /v1/deb/repo

/rep will default to a single repo/xml directory. The goal would be manage multiple repos by utlizing a name query parameter as such:

curl http(s)://<yum-nginx-api-server>/v1/rpm/repo?name=dev
curl http(s)://<yum-nginx-api-server>/v1/rpm/repo?name=prod

By adding this functionality for both multi-RPM/Deb repos we could add a UI layer built into the binary that looks like this: https://yeticloud-artifacts.s3.amazonaws.com/index.html

If it's worth adding an index web server for other assets/artifacts that are not RPMs and Debs I'm also open to this.

Additonal diserable configurations are:

  • HTTPS/2 support
  • Additional HTTP/SSL configurations
  • CLI/ENV VARS/YAML configurations
  • Promethus endpoint
  • S3 support
  • DevOps artifacts (Docker/Vagrant/install.sh)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment