Lucee 5.4 feedback; Docker and Heroku


#21

Very timely joke tweet:


#22

:+1:

It’s great that I can drop a *.lex into the deploy directory, but it really stinks that the installation process is so “secretive” that one can’t know it’s finished but through trial-and-error heuristics.

Sure, I solved the CFSpreadsheet installation puzzle a while back (after probably 8 hours of total effort spent after using other methods proved less than 100% reliable), but now I’m about to play with redis, and I dread figuring out what time and black magic I’ll encounter with the effort.

I really hope somebody responds to this and tells me that I’ve missed something, and that third-party extension installation is actually straightforward.


#23

I’d like to see consideration to making all the web admins available under a single url.

With with cdn/proxies, clustering, load balancers etc it can become rather tricky to access
a web admin, especially when locking down access to the lucee admin via ip address.

https://luceeserver.atlassian.net/browse/LDEV-924


#24

In our Docker clusters we go the opposite way, we have no reason to ever allow access to the Lucee admin and so we want it to be completely disabled/unavailable in production environments. It would be great to have a build where it’s simply not present at all, or at the very least can be completely disabled by an environment variable, rather than removing mappings or using the web server to secure it :slight_smile:

I can see how that ticket might be useful to server installs with many apps in a single Lucee instance, but in a container environment I think it’s less useful as each app runs in it’s own container. Exposing the admin is generally a bad idea, but particularly with Docker then configuration should come from the image and the environment, rather than twiddling settings in the admin.