Similar to: #9
What are the steps to reproduce this issue?
- Create a new app using the Ortus Module Template
- Add a server.json file to the project root and make sure the web.webroot value is set to test-harness.
// example server.json
{
"name":"myapp",
"app":{
"serverHomeDirectory":".engine/lucee5",
"cfengine":"lucee@5"
},
"web":{
"http":{
"port":"60301"
},
"rewrites":{
"enable":"true"
},
"webroot":"test-harness",
"aliases":{
"/moduleroot/myapp":"./",
"/modules/myapp":"./"
}
},
"openBrowser":"false",
"cfconfig":{
"file":".cfconfig.json"
}
}
- Start the server from the root
- Enter
coldbox watch-reinit in Commandbox
What happens?
Console will display:
Server Status: Stopped
Would you like to start it [y/n]? :
What were you expecting to happen?
The Coldbox-CLI should identify that the server is running in the webroot and watch the specified folder for changes.
Any other comments?
Discovered this when building a Coldbox module where the webroot lives in "test-harness", but I want to monitor the project root (the module's code) for changes so I can reinit the test-harness.
Similar to: #9
What are the steps to reproduce this issue?
coldbox watch-reinitin CommandboxWhat happens?
Console will display:
What were you expecting to happen?
The Coldbox-CLI should identify that the server is running in the webroot and watch the specified folder for changes.
Any other comments?
Discovered this when building a Coldbox module where the webroot lives in "test-harness", but I want to monitor the project root (the module's code) for changes so I can reinit the test-harness.