I’m missing a default Application.cfc template in the offical docs. At least I didn’t find any. Going to add it to the docs as soon as I get some time to contribute.
Welcome to modern cfml. I understand the problems you are facing, because I was also at that exact point some time ago. Don’t give up. We from the Lucee Community are here to help.
In the Application.cfc you need to start ditacting with the component tag:
To start with an empty template, I’ve just found this wonderful git repository with a default Application.cfc
Also look into Lucee Application.cfc documentation which explains all functionality. Here is the tag referrence for Application.cfc
I think yes! Shouldn’t be a problem. No need to change all your legacy application code to .cfc’s. Just the Application.cfc should work. However, some new application stuff only works within a modern Application.cfc. But other legacy coded stuff should simply work, unless its some type of edge casy code where you might find some issues.
Not at all. You can create them in your Administrator, However, as soon as you do it, copy the generated code (you’ll find it in the Lucee Admin after creating it) to your Application.cfc. Do the same with everything else: Session settings, Charset settings, Mappings etc. Use the “Application Export” section to do it. Doing this you will ensure portability of your application because these settings are backed up when backing up your www root. Sometimes you need to wipe out the server context or the web context (e.g. may happen on up-/downgrades and these usually wipe out your settings of the Lucee Administrator. When having the settings stored in your Application.cfc the settings simply will persist there.