Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future enhancement idea: Easy way of making custom repositories #773

Open
Daniel15 opened this issue Oct 12, 2016 · 3 comments
Open

Future enhancement idea: Easy way of making custom repositories #773

Daniel15 opened this issue Oct 12, 2016 · 3 comments

Comments

@Daniel15
Copy link
Member

One of the things I love about Linux repositories (such as Debian and RPM repositories) is that it just consists of plain files and there's no custom server-side component at all. There's a few files that contain metadata about all the packages, along with the actual binaries themselves (eg. .deb for Debian, .rpm for CentOS). This makes it super easy to host a repository as long as the metadata is built correctly. You can even host a package repo on a plain basic webhost such as Github Pages.

It would be awesome to have something like this for Yarn too, a simple way of making a custom package server. "Throw these files onto a server somewhere" is a much easier deployment strategy than running some custom server software and having to worry about keeping it up-to-date with security patches etc.

Related: #547 (support for multiple servers), #606 (number of stars on this issue means a lot of people are using custom servers already)

@gsklee
Copy link
Contributor

gsklee commented May 26, 2017

@Daniel15 If you're still looking to pursue this idea, the scale of this feature request means that it needs to go through the proper RFC process.

@Daniel15
Copy link
Member Author

Daniel15 commented May 26, 2017

Yeah... This issue was created before the RFC process was finalized, hence why it's in the repo.

I don't think I'll have time to flesh it out soon... Happy to help someone with it though. Maybe one day I'll have enough time to write up an RFC 😛

@gsklee
Copy link
Contributor

gsklee commented May 26, 2017

Well in that case, is it safe to say that we can close this issue for now? I'm helping out with #3474 :-p

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants