As a package script in box.json of a server script in sever.json

If you're asking if there is a way to export those dependencies into box.json like cfconfig allows you to do with settings, no, I do not believe there is any way to do that.

basically I have numerous devs that I want them to be able to just grab repo and run start and the app works...not having this extra step grab and reinstall those CF packages every time they start the server

lucee extensions go in dependencies and the URLs are just prefixed with lex: ... i wonder if there is a cfpm: equivalent?

I'd assume you could just change "install:2021" to "onServerInstall" to make it run automatically.

Thanks a bunch man!

good luck!

Which you would access as explained here: https://commandbox.ortusbooks.com/package-management/package-scripts#access-intercept-data

FWIW, I didn't do that example in the coldbox repo-- Luis did that and it seems he made it unnecessarily complex 🤔

There's no need to manually reference the actual .sh script, which isn't even going to work on Windows! Instead, you only need to use the built in

cfpm

command which automatically defers to the actual script or batch file for you.

As far as wanting Adobe CF 2021 to work like Lucee, that's not going to really happen • cfpm installs actual jars, not just "settings" in an XML file somewhere • So CFConfig can't manage them because at the end of the day, CFConfig just edits XML files for you, it doesn't store or download jars • Lucee has the deploy folder so you can just drop lex file on disk and they will install, but Adobe CF does NOT do this • Lucee has the

LUCEE_EXTENSIONS

env var so you can just set the env var and it will install, but Adobe CF does NOT do this (outside of the Adobe-specific docker containers) • All ACF has is the

cfpm

CLI tool (which ironically, Lucee does NOT have) so there are a lot less options of how you can install your ACF packages

So for Adobe to work • The adobe engine has to already be installed, unlike Lucee. This is why we use the

onServerInstall

package script • You basically only have the option of running the cfpm CLI tool to install them

Really, ignore all the weird complexity of that Coldbox repo-- you should just need something like this in your

server.json

(starting in CommandBox 5.5.0, you can have server scripts in your

server.json

that work the exact same as package scripts in your

box.json

, but only apply to server-related interception points and are obviously specific to that server.)

server.json

{
  "scripts": {
    "onServerInstall": "cfpm install orm,zip,docuemnt,mail,debugger"
  }
}

Or if you want to get fancy, do something like this (just typing this off the top of my head)

{
  "scripts" : {
    "onServerInstall" : "assertFalse \${interceptData.installDetails.initialInstall} || cfpm install orm,zip,docuemnt,mail,debugger"
  }
}

@Patrick @bhartsfield