Option for server start to write file with full start args for direct Runwar call
Description
This will allow you to capture the exact args needed to fire runwar completely outside of CommandBox. So you can do a dry run start which processes CFConfig, CF engine downloads, Fusionreactor installation, and even env variables and then save the actual start script for later.
Later directly from bash...
Support bash, cmd and powershell, each of which use different escape sequences and different syntax for declaring environment variables.
This feature completely “locks in” the exact args to start the server so any later changes to your server.json or even new versions coming out on Forgebox will have no effect as it bypasses all the normal server start and CFConfig logic and just directly hits runwar. This also means no CommandBox interceptors or package scripts fire. They fire when creating the script, but not when you run the script. It’s all just pure runwar at that point.
Activity
Show:
Brad WoodJanuary 18, 2020 at 1:09 AM
Fixed
Pinned fields
Click on the next to a field label to start pinning.
This will allow you to capture the exact args needed to fire runwar completely outside of CommandBox. So you can do a dry run start which processes CFConfig, CF engine downloads, Fusionreactor installation, and even env variables and then save the actual start script for later.
Later directly from bash...
Support bash, cmd and powershell, each of which use different escape sequences and different syntax for declaring environment variables.
This feature completely “locks in” the exact args to start the server so any later changes to your server.json or even new versions coming out on Forgebox will have no effect as it bypasses all the normal server start and CFConfig logic and just directly hits runwar. This also means no CommandBox interceptors or package scripts fire. They fire when creating the script, but not when you run the script. It’s all just pure runwar at that point.