Not sure if I’ve got something wrong here, but I’m sure this has worked before…
I have a new site which I have set up to use Lucee@5.2.5. This is my server.json file, in the root of the site:
`
{
“app”:{
“cfengine”:“lucee@5.2.5+20”
}
}
`
Surely with that in place I should be able to simply use box server start, and it will use the specified version of Lucee? But it launches using Lucee 4.5…
If I use box server start cfengine=lucee@5.2.5, it works fine.
That should work fine. Are you running your “start” command from the web root? Add --debug to the start to see some information on what server.json file is getting used. Report back the full console output here.
So, if I do server set app.cfengine=lucee@5.2.5, it creates a file server.json.
However, when I start the server, it looks for a server file with the site path in the filename:
Looking for server JSON file by convention: /Developer/www/cryotag.co.uk//server-cryotag.co.uk.json webroot specified by user: /Developer/www/cryotag.co.uk/ start server in - /Developer/www/cryotag.co.uk/ server name - cryotag.co.uk server config file - /Developer/www/cryotag.co.uk//server-cryotag.co.uk.json
Why is it looking for this file? And can I make it just user server.json?
By default, CommandBox will look for a file named server-.json. This makes it easier to have more than one named server in the same folder. Does a file of that name exist?
And can I make it just user server.json?
Well, if server-cryotag.co.uk.json exists and you don’t want it being used, then delete it! More specifically, you can always do this:
That doesn’t make any sense. Why would you tell a server.json file how to find itself? Please refer to the docs for the list of valid properties in your server.json.