forgebox registerif you don’t have one)
publishcommand from that folder.
box.jsonor it will be updated. Review our generic docs on how to creating and publishing packages here: https://ortus.gitbooks.io/commandbox-documentation/content/packages/creating_packages/creating_packages.html
box.json, you’ll want to minimally have the following properties set:
slugproperty in your
box.jsonto be the unique GUID of your extension from your manifest file. Lucee's docs state this needs to be a UUID. It needs to match what’s in your manifest or updates won’t work.
versionneeds to be the current version of your package that you want to publish. To add a new version, you’ll just update the json and re-run the
publishcommand. One thing to watch out for is that Lucee likes to use the
x.y.z.qversion format which does not quite match the npm-style
x.y.z-prerelease+buildformat of ForgeBox. I usually stick with just three digits
x.y.zso it’s compatible across the board.
typeproperty in your json to be
thumbnailproperty in the json
locationproperty in the json. Please note Lucee has some bugs where it doesn’t like servers that don’t set the right content type that it expects. Someone else I was helping had to rename it to a zip file on GitHub so get Lucee to accept it. (A lex file is just a zip file) Perhaps go give a vote on this ticket.
publishcommand will pick up any
readme.mdfile in your current directory where you run the
publishcommand and will put it on ForgeBox as the description. This is very handy so make sure you have a good readme so your package home looks good. If you want to update it, simply edit the readme file and re-run the
publishcommand at any time.
box.jsonand the ForgeBox Lucee Extension provider will pick them up and report them. Please refer to the Lucee docs on what each of these do.