Skip to content

Coldbox Watch-Reinit Doesn't Recognize Webroot Setting in server.json #76

Description

@homestar9

Similar to: #9

What are the steps to reproduce this issue?

  1. Create a new app using the Ortus Module Template
  2. 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"
}
}
  1. Start the server from the root
  2. 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.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions