Thank you Terry. TBH that is more like I did things in ACF. Each version of each site (Dev, staging, production) had identical code except for a small variables file that contained things that were different. They were turned into Application vars when the application was refreshed . If i can make that work the same way with Lucee, thats one fewer change i have to make on the migration.
I can see lots of things i would like to do going forward to take advantage of newer.better ways to do things but today I just need to get everything migrated and working as it has been. Then i can take my time reworking the oldest, least efficient code.
Yes, of course you can setup the datasource in the Lucee administrator. What I was trying to say is, that many admins today may use the administrator to create the datasource once only: Then, from inside the administrator and after creating that datasource, you will be able to copy and paste the datasource definition code for that datasource into your Application.cfc. With that datasource definition code in place of your Application.cfc you won’t need to recreate that datasource in your administrator again, bcause your datasource settings will be picked up directly from within your Application.cfc. Doing it that way, you have much better portability of your web application…
Thank you Andreas. I have read that information in the Lucee docs. I need to have 11 sites going nearly all the time on my dev machine because i maintain them regularly, and some more i maintain infrequently. THen i need to be able to upload any changes to my production server and know that they’re going to work FOR SURE
And i need to have all 11 going simultaneously. That means (I think ) that i need to have at least 11 Lucee servers running if i use the Command Box to control them. Wouldn’t it be better to do it the way I used to run Adobe ColdFusion with one server but numerous datasources configured there?
Not necessarily. Previously CommandBox followed a Docker mentality, where one server/JVM/java process had a single web root.
This has all changed in Commandbox 5.5.0 (released yesterday) with built in Mod CFML support. Install BonCode into IIS (globally if you’re only using Lucee, or per-site if you want Lucee and Adobe side-by-side) and then enable Mod CFML support in CommandBox with
server set modCFML.enable=true
server set modCFML.sharedKey=your-key-here
Then enable AJP in CommandBox
server set web.ajp.enable=true
and set the same shared key in your Boncode settings XML file. (In the BIN folder of each web root if Boncode is installed per-site, or in the C:/Windows folder if installed globally) Now, define your sites and web roots in IIS like you normally do and CommandBox will auto-created contexts for each site and you can do it all on a single server.
Regarding your question about configuring datasources, I mentioned this above, but perhaps you missed it. CommandBox has a module you can install called commandbox-cfconfig that allows you to export/import/compare all configuration in a JSON format. So whether you want to create the datasources initially in the web admin UI and then export them to JSON or create then entirely from the CLI with the cfconfig datasource save command is entirely up to you. But once you start using CFConfig, you can start a server fresh for the first time and have the configuration automatically imported and ready to go without you ever touching the admin UI.
Good lord, every time i ask a question i end up with a whole new can of worms.
I dont know anything about Docker except what it is and I’ve loaded a few Docker projects. So i dont know what the Docker mentality is.
Now there’s another new app to download - Commandbox 5.5.0, while I was assured that the previous version would be the bees knees. Now i have Mod CFML (whatever that is) to learn about as well as a new CommandBox. What IS MOD-CFML ?
And what’s BonCode? Why do i need to know about that too? How many other things do i have to learn about just to get back to where I was last Wednesday? And i can’t go back to using ACF because loading something along the way here has broken that too. So even my old configuration doesnt work now.
And apparently I cant install Lucee on my WIn10 system because despite everything I do it still insists that TomCat is already a service when it isnt. No one seems to have an answer for that problem. I’ve asked here several times an dno one’s had a go at explaining it or helping me solve it.
I’ll say again - all i want to do is be able to get rid of Adobe ACF and get back to managing my client’s sites and my own sites. 11 of them. But in order to do that i need to discover what needs to be changed in the old code to make them work how they used to under ACF. I have been assured for YEARS that with Lucee there are minimal changes needed. However that’s not Zero changes. I need to test all my sites and learn what needs to change on them, so they can be loaded onto my new Lucee server without disrupting my clients’ businesses. Not spend days and days trying to get bloody Lucee to work.
But thanks for your help. I know I’m showing my frustration but i can tell you after spending all this time and getting nowhere near where I need to be I’m beginning to regret the whole thing.
Lol, I get it, there’s a lot of stuff to learn, but I think you’re also overstating it. This is sort of what you’ve signed up for. You want to run Lucee locally. But also with Adobe CF. And also with IIS. And also 11 sites. There’s no path to here wihtout you learning some new stuff. There’s also like 37 possible ways to do it and you’re getting a mixture of advice from a mixture of people. CommandBox is, in my biased opinion, still the shortest distance between two points for you, but it’s still going to require some new things being learned. A lot of what yoiu’re used to on Adobe is either a proprietary setup, or hacked together version of Tomcat (Adobe compile their own custom Tomcat to make stuff work a certain way), and some bits of the architecture simply won’t look exactly the same in Lucee-land.
Honestly, I told you precisely what it meant.
It is. And 5.5.0 is the bees elbows too.
It’s an proxy setup for Lucee (or really, any java app) that is comprised of
A Tomcat Valve (for people using Tomcat)
A CommandBox feature you can enable (for people using CommandBox)
An IIS module called BonCode (for people using IIS)
An Apache module (for people using Apache)
A specification of custom headers you can add (for people using Nginx or any other web server)
It is the equivalent of Adobe’s special AJP-based IIS wsconfig connector which proxies traffic from the front end web server to the CF server and auto-creates contexts based on the web root defined in the front end server. Adobe CF people are just used to that being the way things work, but the rest of the Java/Tomcat/etc world don’t work that way and have never worked that way.
Well, no one is making you learn about it, but it’s the most common, most documented, most familar approach for Lucee users who want to front their server with IIS. You can certainly configure your own HTTP proxy with IIS’s request routing, and configure your own HTTP headers if you like, but BonCode is a pretty nice library to help you do all that with less work. It’s up to you.
Probably about 37. It will be fun though. And once you have it all working, it won’t seem nearly as daunting.
No one said being a server admin (even if it’s your local servers) was always going to be easy. You’re not necessarily making it easier by wanting to have IIS in the mix, but it’s your call. Adobe has spoiled you a bit, but it’s really not that much harder to set up Lucee. Doing them side by side is completely possible, but you’ll need to step up your game in regards to how much you understand what’s going on under the hood. It does take at least a nominal amount of fiddling.
All I can find is this thread created less than a day ago on a weekend. People in this forum help for free, unless you want to buy some consulting hours to have someone help. Zac is your best bet to figure out the installer stuff as he’s the guy currently helping maintain them.
It’s ok, keep your head up and push through. But maybe after taking a break, lol. There are plenty of people willing to help explain all the bits and pieces here and I’m sure you’ll get it all figured out soon. I think perhaps you’re expectations were a little off in terms of what you’d need to learn, but you’ll get it soon enough.
@bdw429s WAIT!!! Are you saying that CommandBox is NOW able to run different webroots within just one single CommandBox instance?? If so, then this is an absolute game changer Brad!!! Especially for those guys who host own sites and want to host different applications within one single JVM instance.
Thank you bdw429s. You’re far more generous than I deserve. I know i’m bitching and it’s not a help. i’m sorry.
I dont actually want ACF at all I have it now. I’ve been working with ACF since v4.0 which is I think 25 years but finally I’ve got sick of being all alone with no one to help me, and it costing me several hundred bucks a month to have an ACF server. All my current work is, to verify that my sites will work on Lucee as they have under ACF (or a reasonable equivalent) and then get rid of ACF comletely goodbye, it’s been nice, dont let the door hit you in the ass on your way out.
Moving into the future (see how i avoided a corporate buzzword there?) I want to be able to manage the 11 sites i have responsibility for, and any other that might come along in the future. I see lots of opportunities with Lucee that either i didnt know about or didn’t exist under ACF. n My dev environment consists of a bigass Win10PC and some laptops of varying age and power and i want to be able to make changes to my current code, upload to the production server with the minimum of fuss. (i.e. I want to concentrate on building web sites and helping my clients build their businesses not on running a server.)
As you say there are 37 ways to do that, as I’m learning. Also as you say, I expect once i get it set up I’ll like it. It’s precisely the way it happened with my existing setup. I guess i’ve been trying to build a Lucee environment to match my ACF environment when really what i ought to be doing is learning a way to use Lucee to achieve what i want - efficient managment of my web sites.
So: [A] if i use the CommandBox approach to this - suppose i need two or three web sites being worked on simultaneously on my machine (yes it happens- humour me ) am I going to have to start a copy of CommandBox in the root of each of those sites? I notice that when i start a server, it opens a home page for teh site on a url like http://127.0.0.1:53786 But another site opens with teh same address but a different port. I get why that is, but will it always be the same port number?
[B] Are you saying i ought ot just do away with IIS altogether? If so, on my dev machines as well as my Viviotech server? ( I Guess Viviotech knows a LOT more than i about what I’ll need but i should ask)
Thanks again for helping me, and I’m sorry i let my frustration get away with me.
@mikek all depends very much how you want to setup up your environment. Comparing with 20years ago, you have way lot more options to develop and run cfml. You can run it the classic old way, or use pure jvm containers, run it with CommandBox, run it with docker, or setup some type of hybrid way.
Most work you’ll have to find the best option or flavour that fits your needs.
I was there too, I’ve modernized my setup, but’s more a “hybrid” classic way. Today I develop locally the npm way (using webpack & co with sass, tailwindcss, ES6 using the -watch option, sourcemaps etc), and the final bundled (minified) files get deployed locally to get deployed per sFTP to the prod servers the old style. I love it that way, because from my perspective you can use all the modern npm dev development stuff all together with CFML. Maybe it’s time to share that somehow somewhere.
At the moment I’m restricted to the Classic Old way because i’m working with client’s working businesses. I have to move to a new server because Viviotech want to take the existing one away and throw it in the trash its that old. So I dont have time to do any development now. I just need to get everything on the new box and running the way it was on the old box. THEN I’ll look at other ways to do web development, and improvements i can suggest on the client sites… Frankly all these things have motivated me the way i havent been motivated in a long time. Maybe I’ll be coming back to you looking for help then.
In the mean time, i have these two questions i need ot decide about. Can you help me with those please?
I have installed Lucee. Not the latest version - but the version previous. I think the issue might be to do with the 188.8.131.52 Install.exe file.
I cleared out all Lucee files and emptied my Recycle bin. I checked nothing was left still running. I used Regedit to remove any records in the registry containing the string 'Lucee" or “Tomcat”. Then I restarted my machine and began again.
I still got the same error, tellilng me “:Unknown error while running c:\lucee\AJP13\Connector_Setup.exe /Verysilent /suppressmsgboxes /log /sp- /nocancel /norestart” I went to run Connector_Setup.exe without the /verysilent option so I could see any error messages as it ran. Only there wasn’t a connector_Setup.exe file to run, or even a AJP13 directory.
I thought it’s a possible fault with the Installation.exe so i repeated the delete-and-erase-the-registrry routine then downloaded the previous installer, version 184.108.40.206 This installation file installed completely in about 1.5 minutes and opened a “Welcome to Lucee” page.
Progress!!! Now I need to learn how to make IIS work happily with the Lucee server and I’m away at the races1!!
What’s the procedure to report this possible problem with the installation file for v220.127.116.11 ?
Thanks. I am pleased to have got past the installation of Lucee after 4 days now. But that’s as far as I’ve got. I can’t see how to make IIS connect web site files and Lucee server.
The videos might be useful but they are only for Windows Server and dont cover IIS on Windows10. The two versions of IIS are quite different. For example the first part of the video playlist is about setting roles in IIS. There’s nothing whatsoever in the Win10 version that’s about roles. And as far as I can see there’s no text file help for that either. So I’m stuck how i was before, but about 2 paces further on that’s all.
(Sigh) that;s 6 days on this now and i havent got a single site running.
@mikek So if you are going the Boncode/mod-cfml route, then you are funneling them through a single Lucee instance (which is the traditional Adobe CF way you’re using to). If you want each site separate (which is what I do for local dev) and don’t need all the sites on all the time, then you just fire up what you need when you need it
server start site-6
// fix some stuff...
server stop site-6
I actually have 226 local CommandBox servers right now because I’m testing stuff all the time. They are all 100% isolated and I can start/stop them whenever I want with whatever settings I want, and then server forget them when I’m done. (I usually forget that last part, lol)
For people who use CommandBox for 1 or more instance in production, you can create a Windows service to start the site (and we have a paid module that helps with that as well)
So with CommandBox, you can pretty much customize and configure every possible thing you can think of, but out of the box if you just say, “Hey start a server!” then we just default the heck out of stuff. We’ll bind the site to localhost and pick a random-unused port on your machine. The same port will be re-used until you forget the server, but you can choose any port you want as well
And that’s just the basics. There’s a handy module called commandbox-hostupdater that will add all your local sites to your hosts file for you so you can set any web.host you want. And even better, that module binds every site to a different 127.x.x.x IP so you can re-use the same port on all sites if you want. Just one of the 37 ways to do it, and a very popular one for local dev.
# one-time install
# one-time set global default HTTP port for all sites
config set server.defaults.web.http.port=80
# set up a specific app
server set web.host=dev.mysite.com
** for the example above to work you’d need to have IIS stop binding to all adapters on port 80.
I’m saying you can if you want. I really like my local dev setups to be as darn simple as possible with as new moving parts, and as few dependencies on any operating system specific web servers (looking at you, IIS). CommandBox has an enterprise level web server built in that uses JBoss Undertow (by Redhat) and it does rewrites, HTTPS, AJP, virtual directories, basic auth, and secure lock-downs out of the box with nothing else you need to install or configure outside of your server.json file. This means a Mac dev and Windows dev can all work on the same local site and then deploy it to Linux and you don’t have 3 separate setups you’re managing.
Now, a lot of people still use IIS because it’s what they’re familiar with, it’s what their ops team knows, and they’re just so used to using it that they think they need it for some reason. I’ve done site-by-side performance tests on IIS, CommandBox/Undertow, and Apache httpd and they all had the same throughput. And CommandBox’s web server is the only one that’s secure-by-default with a built-in CF-aware set of lock-down rules. So basically, you can do whatever is easiest for you, but CommandBox CAN be your one-top shop for a complete, portable local dev environment.
Yes, it’s possible to host on CommandBox in production, but just to simplify, I’d worry about dev for now. To be Honest, Vivio’s staff probably knows very little about CommandBox. They usually have a guide they are used to following for setting up and configuring CF, and it uses the standard Lucee installer.
The Old classic way works and doesn’t cause you glaring security headaches, nor keep command line history, nor timestamp everything down to the millisecond, or agree to licensing terms and conditions on your behalf.
Just like old coldfusion, you backup your config files and code and you are fine.
As I understand it, Mike has some sites using Lucee and some using ColdFusion on his DEV computer and he prefers to use IIS for both. An alternate way to have both Lucee and ColdFusion sites using IIS on the same DEV computer is to set the handler mappings at the site level defined in web.config rather than the default top IIS level.
I have Lucee and BlueDragon both running on IIS on the same DEV computer. The same principle should apply to a Lucee and ColdFusion mix. After installing both Lucee and BlueDragon remove the Lucee related handler mappings at the IIS top level then at the Lucee site web.config remove the BlueDragon handler mappings and replace them with Lucee’s as in the example below.
Peter is correct. And to be clear, that’s also what I suggested 2 days ago
but perhaps it wasn’t clear. Just like Boncode, Adobe CF’s wsconfig tool also lets you choose only the sites you want it to proxy. To run all your sites side-by-side you’d basically need to create two versions of each site in IIS on two different host domains, each one proxying to either Adobe CF or Lucee.
Thanks, I"m 'gradually getting there. I think you guys in this community (Generally not specifically you personally) are more used to people a lot more knowledgeable about the nuts and bolts of servers. I’ve spent my most of my last 20 years or so building actual sites and coding people’s pages rather than concerning myself with the intricacies of servers. Once I had my server set up i have tended to leave it and get on with site building, and so it’s not been something i’ve touched very often.
I dont want to have both ACF and Lucee going simultaneously. At least not once I’ve finished the migration to Lucee. I want rid of Adobe from my life completely. (After I get this migration out of the way I’m starting on finding alternatives to Adoobe Audition and Photoshop. )
Here’s why i need to have several sites running at once.
 I have my CMS and my public sites in separate sites. So i need to be able to be running some maintanence in site cms.clientsite.com.au and be able to check the overeall result in clientsite.com.au and go back and forth between them (Yes i know that’s old fashioned and could be done better in one site - but i have what i have and i’ll totally rebuild another day)
 i have quite a few tools - code writers, syntax checkers etc - written in cfm in their own web site. I’d like to be able to have that site running too.
 the software i use to run my radio shows is written in cfm. When I’m on the air i need that going at the same time as the site that’s the public facing site for the show, so i can go back and forth.
All of these can be re written. But not in a day or so. Right now i just need to get migrated to Lucee and run them as before with the minimum number of changes Then come back and look at updating them or changing the way they work when i have this migration out of the way. Does that make sense?
Perhaps it’s my fault for not saying i didnt understand it.
I’ve changed my web.config to read like this. And IIS is not running now. How do i set Command Box to allow me to run several Lucee sites at once? I have CommandBox 5.5.1 running sweet and fast. I love this now!!! I’m nearly at the point where I just put my head down and get on with managing the sites and stop worrying about the server end of it.
I know I’m being a bloody nuisance but i’m almost there And i am so very grateful to you.
My Take on Commandbox
Commandbox uses Undertow, good bad or indifferent as the last time i checked they still are using a very outdated and very insecure version of this Java Server. Its a good product for development on some of the most minimal of hardware, but I wouldn’t dare put anything in production on something that has a known glaring security issue.