Open code-kungfu opened 5 years ago
I have no intention of turning this thing into a store, that's the last thing I want to do.
The package server protocols will be open source, so commercial vendors would be able to implement their own package feeds and provide credentials to customers, or just make the package binaries available for download to customers via some other mechanism.
The first iteration will be to get a folder to serve as a package feed! Then we'll follow that up with remote package feeds/public registry.
Having the packages hosted elsewhere (ie not on the package server) might be an option we can explore.
There is no need to reinvent the wheel. The architecture used by "Composer" and "NPM" is simple and efficient. In both packages repository works as a DNS, they only return information on how and where to download the files that are usually hosted on Github, Gitlab, Bitbucket or SourceForce. There is also the option to add dependency on local repositories and shared folders on the network.
Drawing inspiration from the Joomla CMS modular update system. Your extension basically adds an URL pointing to an XML file hosted at the vendor and updated when a new version has been made available. In essence a RSS feed. For most paid extensions, you're provided with a key you have to insert in order to download updates.
Would it be an idea to implement something similar, so the hosting of the package itself is located at the vendors website/CDN and not the registry itself?