Hi Robert, I see Luis replied a bit to you on the CommandBox list, but I’ll
reply here as well for the sake of anyone not on the CommandBox list.
Regarding the ability to register packages from the CLI, this is on our to
do list for ForgeBox for sure. We’ll announce when it’s ready so people
can help us test and use it.
Regarding ‘existing’ libraries, CommandBox has a very flexible system for
retrieving packages via ‘endpoints’. While we haven’t developed any
endpoints for sites like riaforge or cflib, we do have the following:
- ForgeBox slug
- HTTP(S) URL to a zip file
- Local zip file
- Local folder
- Git repo
This gives you a lot of options with just about any existing library on the
internet. And unlike NPM, CommandBox will still install packages even if
they don’t have a box.json, though it will complain a bit. We have a lot
planned for ForgeBox including paid private package and ForgeBox Enterprise
so to be honest, we’d rather look at what needs to be done to make ForgeBox
allow for everything you need rather than making a bunch of custom
endpoints for other sites that aren’t nearly as advanced.
Thanks for the feedback!
~BradOn Monday, October 19, 2015 at 2:10:34 PM UTC-5, Robert Munn wrote:
Posted to the CB list but thought I would post to this list for feedback,
I have been thinking about ways to make the package manager better. I
would love to be able to install packages from RIAForge, cflib.org, or
any arbitrary code repo like github from the package manager.
I would also love to be able to add a package to the registry via CLI like
bower allows you to “bower register foo ”. This would have the
dual purpose of enabling mass registration of all the packages at a given
site, e.g. cflib. Lots of details there, I know, just thinking it would be
worth making the package manager more open.
The current method of registering packages feels a bit clunky.