I see some threads about deploying Lucee on AWS using OpsWorks back in
February but don’t see too much chatter about it since. Over the past few
days I have played around a little bit with adapting Roland Ringgenberg’s
Railo / Lucee Cookbooks (ringgi (Roland Ringgenberg) · GitHub) but they don’t seem to
entirely work out of the box on OpsWorks instances.
Roland’s cookbooks work by downloading the Lucee Jars and configuring
Tomcat to use them, but the OpsWorks workflow is perhaps more suited to
deploy applications as WAR files. However, I also like the idea of a Lucee
Cookbook that will just drop Lucee (as Jars) on an OpsWorks controlled
instance without having to worry about bundling up everything into a WAR
file. This also allows multiple CFML applications to be deployed without
having to bundle all of Railo up into each one.
I prefer not going the route of using a custom AMI since in my opinion that
sort of defeats the purpose of Chef is that it can build up the machine for
you from nothing (instead of relying on a special AMI).
Is anyone else using OpsWorks for Lucee deployments and/or have additional
opinions or input?
What I really, really wanted to see was an example of how to manipulate the
stock Lucee WAR to become a configured Lucee with a nice, obvious space for
my codebase, suitable for script-driven creation and ready to just blithely
hand off to either my own fresh Tomcat or OpsWorks or what have you. I’ve
never seen that, but that’s what I feel the minimum would be for me to be
comfortable with WAR-based deployments. If I can’t automate it I won’t do
it.On Friday, August 21, 2015 at 11:07:42 AM UTC-5, Cameron Childress wrote:
Is anyone else using OpsWorks for Lucee deployments and/or have additional
opinions or input?
We used opsworks for a client prior to our move to docker. Our chef script
uses the installer as opposed to the war file and we commit server xml and
config files and deploy them from bitbucket as part of the base recipes. So
after install, they get copied into the appropriate folders.
lucee.rb - Pastebin.com is a recipe with some paths and password
redacted. This was recently converted from railo, so not sure if this
version has been tested but should work and if not will give you a solid
starting point in any case. Obviously some of the pre-requisites are
already downloaded by other recipes e.g config files etc.
We cdn all our files incidentally, as you don’t want to be reliant on third
parties that might be down at server up time.On Saturday, August 22, 2015 at 2:07:42 AM UTC+10, Cameron Childress wrote:
All-
I see some threads about deploying Lucee on AWS using OpsWorks back in
February but don’t see too much chatter about it since. Over the past few
days I have played around a little bit with adapting Roland Ringgenberg’s
Railo / Lucee Cookbooks (ringgi (Roland Ringgenberg) · GitHub) but they don’t seem
to entirely work out of the box on OpsWorks instances.
Roland’s cookbooks work by downloading the Lucee Jars and configuring
Tomcat to use them, but the OpsWorks workflow is perhaps more suited to
deploy applications as WAR files. However, I also like the idea of a Lucee
Cookbook that will just drop Lucee (as Jars) on an OpsWorks controlled
instance without having to worry about bundling up everything into a WAR
file. This also allows multiple CFML applications to be deployed without
having to bundle all of Railo up into each one.
I prefer not going the route of using a custom AMI since in my opinion
that sort of defeats the purpose of Chef is that it can build up the
machine for you from nothing (instead of relying on a special AMI).
Is anyone else using OpsWorks for Lucee deployments and/or have additional
opinions or input?