The info command contains useful output, that can be used to:
Lock in the version of the Lucee server
Know the correct path for the runwar JAR
Currently the info command only outputs as text. It would be useful to allow the output of this as either JSON or properties format, that could be used. An additional option to write the information to a file would also be helpful
An example of this would be in a progressive build for a Docker container:
Activity
Show:
Brad Wood September 25, 2021 at 4:24 PM
Jon Clausen March 19, 2020 at 12:03 PM
That works for me, as well. I can always use $(box info --json | jq -r '.runwar.version') or pipe it to a file with echo
Brad Wood March 17, 2020 at 5:10 PM
Great idea Jon. My standard flow for this is to have a boolean --json flag, As far as saving to a file, I’ve always relied on the file redirection functions of CommandBox or bash instead of building a feature into every command that has output.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
The info command contains useful output, that can be used to:
Lock in the version of the Lucee server
Know the correct path for the runwar JAR
Currently the info command only outputs as text. It would be useful to allow the output of this as either JSON or properties format, that could be used. An additional option to write the information to a file would also be helpful
An example of this would be in a progressive build for a Docker container: