How do you deploy your Wheels apps?

[bpamiri]

I'm polling the community in hopes to gain a better understanding of how you deploy your Wheels applications.

One of the things we have implemented in the 3.0 branch (check out the develop branch for the latest checkpoint) is a directory structure re-architecture. This is to enable only putting static files in the root and keeping application files out of the root. The desire for this has been mentioned many times and various members of the community have expressed their wish and desire for such a system.

The issue I have with this is how do you expect to deploy your application. If you are deploying by copying the files to a shared hosting account, typically these types of accounts will have a httpdocs or public directory that they want you to place your files into. If you are deploying via a docker image, are you using CommandBox to host your application in the Docker container? With CommandBox we can utilize the server.json file and use the web.webroot element to specify the public folder should be the webroot of the application.

So the dilemma is this, should we make the base structure one that makes FTPing the files to a shared account easier or should we make the base directory structure one that makes usage via CommandBox easier? Sense we are advocating the use of CommandBox for development it makes sense to follow suite for a deployment architecture, but I don't know how this might effect potential users.

I could also envision additional command line options that may deploy the application onto different platforms and arrange the directories into a way that makes sense for each platform.

[chapmandu]

We deploy with docker and commandbox. I'd lean heavily toward modern, secure best practice.

[tsucaet]

We’ve just migrated our Wheels applications to the latest Lucee 6.x using CommandBox, without a proxy web server. Currently, we deploy directly on a Linux server, but we haven’t yet moved to a Docker or containerized environment.