Skip to:
This server.json example...
should be relative to the folder that the server.json lives in, not the web root. The docs say web root:https://commandbox.ortusbooks.com/embedded-server/configuring-your-server/aliasesBut that conflicts with what this part of the docs say https://commandbox.ortusbooks.com/embedded-server/configuring-your-server#file-path-handling
Since this is a breaking change, make it be a cascading lookup that favors the old behavior
Check paths relative to the web root and see if that folder exists, if so use it
Fall back to checking paths relative to the folder that the server.json lives in
At a later point (major release) we can remove the fallback and have the behavior always check the right place.
Also note, paths specified in a global config default are always relative to the web root.
This server.json example...
should be relative to the folder that the server.json lives in, not the web root. The docs say web root:
https://commandbox.ortusbooks.com/embedded-server/configuring-your-server/aliases
But that conflicts with what this part of the docs say
https://commandbox.ortusbooks.com/embedded-server/configuring-your-server#file-path-handling
Since this is a breaking change, make it be a cascading lookup that favors the old behavior
Check paths relative to the web root and see if that folder exists, if so use it
Fall back to checking paths relative to the folder that the server.json lives in
At a later point (major release) we can remove the fallback and have the behavior always check the right place.
Also note, paths specified in a global config default are always relative to the web root.