I set up a new server yesterday running Lucee 4.5 (Java @1.8.0_45, Tomcat @8.0.24) and have run in to an issue that I haven’t encountered before. The directory structure looks like this:
| appname
| currrent - symlink to ./releases/[current release]
| WEB-INF - symlink to ./shared/WEB-INF
| shared
| WEB-INF
| includes
| tmp
| [other shared/dynamic static asset paths]
| releases
| [current_release]
| [previous release 1]
| [previous release 2]
| [previous release 3]
| [previous release 4]
Deploy scripts create the new release directly and then symlink that to /releases/[current_release]. The web context is configured with allowLinking=“true” and those paths all resolve correctly with Tomcat and Apache, however symlinking the WEB-INF directory results in Tomcat errors app-wide for any CFML files and the admin paths.
I run this symlinked directory setup on several other servers without a problem - all running Lucee 4.2 (Java @1.7.0, Tomcat @7.0.20), which were manually upgraded from Railo, without a problem.
All of a sudden, the new environment with the upgraded versions fail with those symlinks in place.
I’m assuming there’s an “allowLinking” attribute that needs to either be set manually for the WEB-INF directory or needs to cascade from the context, but I’m not sure where that needs to be set.
Can anyone point me in the right direction as to where I might adjust that configuration to enable the WEB-INF directory as a symlink. I’ll be happy to submit a pull request for adjusting that setting as default as well.
Thanks! JC
--
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/etPan.55b520c2.4acbf4b3.e431%40jonclausen-mbp.local.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/CAG1WijW1YWWht5wyLWC%2BwF5044QkrqmQmwoy-dGCT04U2sV5xg%40mail.gmail.com.
Sorry, Jordan, yes. I meant the context.xml file. The WEB-INF symlink resolved correctly only after the following node was added within <Context>:
<Resources allowLinking="true" />
To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/332496340.205944.1438024695699.JavaMail.zimbra%40viviotech.net.