Configuring Lucee for cloud instance

Hello,

I’m trying to work out what the best way to configure Lucee is from a
configuration-managment point of view. I’ve got suitable recipes for
installing and configuration Apache, and I can install Lucee and then put
in my own server.xml and web.xml files and configure the connector myself,
that’s not the problem.

But I’d like to configure Lucee itself before I try to boot my application
on it – set passwords, configure mappings and datasources. So far the
“best” way I have to do this is to create an unserved directory, put a
CFADMIN-employing template in it, boot Lucee, call that template, then
delete that template because I don’t especially want plaintext credentials
anywhere they might get served.

It works most of the time, but it seems a little rickety and certainly it’s
not my preference. I have reasons for not wanting to load the app
configuration into Application.cfc. Is there another way to do this I’m not
seeing?

I’m working on the same issue as well. Besides the points you mentioned,
I’m also looking to install extensions at launch.

Isn’t there some way to do admin actions through command line?On Monday, February 16, 2015, Asher Densmore-Lynn <@Asher_Densmore-Lynn> wrote:

Hello,

I’m trying to work out what the best way to configure Lucee is from a
configuration-managment point of view. I’ve got suitable recipes for
installing and configuration Apache, and I can install Lucee and then put
in my own server.xml and web.xml files and configure the connector myself,
that’s not the problem.

But I’d like to configure Lucee itself before I try to boot my application
on it – set passwords, configure mappings and datasources. So far the
“best” way I have to do this is to create an unserved directory, put a
CFADMIN-employing template in it, boot Lucee, call that template, then
delete that template because I don’t especially want plaintext credentials
anywhere they might get served.

It works most of the time, but it seems a little rickety and certainly
it’s not my preference. I have reasons for not wanting to load the app
configuration into Application.cfc. Is there another way to do this I’m not
seeing?


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+unsubscribe@googlegroups.com
<javascript:_e(%7B%7D,‘cvml’,‘lucee%2Bunsubscribe@googlegroups.com’);>.
To post to this group, send email to lucee@googlegroups.com
<javascript:_e(%7B%7D,‘cvml’,‘lucee@googlegroups.com’);>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/74a62a28-654a-4e78-bda6-e14f71b556f0%40googlegroups.com
https://groups.google.com/d/msgid/lucee/74a62a28-654a-4e78-bda6-e14f71b556f0%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Sent from Gmail Mobile

I was just about to ask about something very similar…

I’d like to know how to set “Inspect Templates = never” during an automated
cloud instance installation.

@Asher, I use the “Expor settingst to Application.cfc” feature and
configure datasources, mappings etc in there.

Regards,
AdamOn Tuesday, February 17, 2015 at 10:15:35 AM UTC+11, Michael van Leest wrote:

I’m working on the same issue as well. Besides the points you mentioned,
I’m also looking to install extensions at launch.

Isn’t there some way to do admin actions through command line?

On Monday, February 16, 2015, Asher Densmore-Lynn <jes...@gmail.com <javascript:>> wrote:

Hello,

I’m trying to work out what the best way to configure Lucee is from a
configuration-managment point of view. I’ve got suitable recipes for
installing and configuration Apache, and I can install Lucee and then put
in my own server.xml and web.xml files and configure the connector myself,
that’s not the problem.

But I’d like to configure Lucee itself before I try to boot my
application on it – set passwords, configure mappings and datasources. So
far the “best” way I have to do this is to create an unserved directory,
put a CFADMIN-employing template in it, boot Lucee, call that template,
then delete that template because I don’t especially want plaintext
credentials anywhere they might get served.

It works most of the time, but it seems a little rickety and certainly
it’s not my preference. I have reasons for not wanting to load the app
configuration into Application.cfc. Is there another way to do this I’m not
seeing?


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+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/74a62a28-654a-4e78-bda6-e14f71b556f0%40googlegroups.com
https://groups.google.com/d/msgid/lucee/74a62a28-654a-4e78-bda6-e14f71b556f0%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.


Sent from Gmail Mobile

What do you need to configure that’s not in the web or server xml config?
just push those up from source control when you deploy.

fwiw, we bundle our apps as standalone packages (app inside railo/lucee war
& tomcat in a jar), mappings are predefined in lucee - web.xml and data
sources are loaded on app init from an external config file (specified as a
system property or loaded from a default location ). The only bit I’m
missing is updating the inspect template setting in lucee-web.xml
automatically when bamboo does a build.

ChrisOn 17 Feb 2015 04:03, “Asher Densmore-Lynn” <@Asher_Densmore-Lynn> wrote:

I know about that, Adam, but it’s not what I want to do. I want the
application to be entirely separate from the credentials it runs under; I
don’t want my cookbooks reaching into and trying to manage an app.cfc
template, or having some really weird branching structure that has /every/
set of credentials in the app repo.

On Monday, February 16, 2015 at 9:50:27 PM UTC-6, Adam Chapman wrote:

I was just about to ask about something very similar…

I’d like to know how to set “Inspect Templates = never” during an
automated cloud instance installation.

@Asher, I use the “Expor settingst to Application.cfc” feature and
configure datasources, mappings etc in there.

Regards,
Adam


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+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/3670f41d-9be4-487f-a36f-c8684fa44556%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3670f41d-9be4-487f-a36f-c8684fa44556%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

I know about that, Adam, but it’s not what I want to do. I want the
application to be entirely separate from the credentials it runs under; I
don’t want my cookbooks reaching into and trying to manage an app.cfc
template, or having some really weird branching structure that has /every/
set of credentials in the app repo.On Monday, February 16, 2015 at 9:50:27 PM UTC-6, Adam Chapman wrote:

I was just about to ask about something very similar…

I’d like to know how to set “Inspect Templates = never” during an
automated cloud instance installation.

@Asher, I use the “Expor settingst to Application.cfc” feature and
configure datasources, mappings etc in there.

Regards,
Adam

@asher Gotcha… Sounds interesting, please post if you get this working…

AdamOn Tue, 17 Feb 2015 15:03 Asher Densmore-Lynn <@Asher_Densmore-Lynn> wrote:

I know about that, Adam, but it’s not what I want to do. I want the
application to be entirely separate from the credentials it runs under; I
don’t want my cookbooks reaching into and trying to manage an app.cfc
template, or having some really weird branching structure that has /every/
set of credentials in the app repo.

On Monday, February 16, 2015 at 9:50:27 PM UTC-6, Adam Chapman wrote:

I was just about to ask about something very similar…

I’d like to know how to set “Inspect Templates = never” during an
automated cloud instance installation.

@Asher, I use the “Expor settingst to Application.cfc” feature and
configure datasources, mappings etc in there.

Regards,
Adam


You received this message because you are subscribed to a topic in the
Google Groups “Lucee” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/lucee/eIvK7YbHjGk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/3670f41d-9be4-487f-a36f-c8684fa44556%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3670f41d-9be4-487f-a36f-c8684fa44556%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

I’ve deployed Lucee to AWS at present through use of a Custom AMI /
Opsworks which seems to work well. To manage deployments I have the
instances automatically pulling in changes from the Mercurial repo.

Originally like you I had a config.cfm as part of my Chef recipes that was
used to configure the individual context datasources etc however it was
certainly not reliable, quite likely due to my inexperience with Chef.

It rather depends just how configurable the instance needs to be, but
ultimately I expect that a combination of Custom AMI / Opsworks / Chef
recipes may well be of use to you (if using AWS - if not then afraid I have
no experience there)On Tuesday, 17 February 2015 17:47:17 UTC, Chris Blackwell wrote:

What do you need to configure that’s not in the web or server xml config?
just push those up from source control when you deploy.

fwiw, we bundle our apps as standalone packages (app inside railo/lucee
war & tomcat in a jar), mappings are predefined in lucee - web.xml and data
sources are loaded on app init from an external config file (specified as a
system property or loaded from a default location ). The only bit I’m
missing is updating the inspect template setting in lucee-web.xml
automatically when bamboo does a build.

Chris
On 17 Feb 2015 04:03, “Asher Densmore-Lynn” <jes...@gmail.com <javascript:>> wrote:

I know about that, Adam, but it’s not what I want to do. I want the
application to be entirely separate from the credentials it runs under; I
don’t want my cookbooks reaching into and trying to manage an app.cfc
template, or having some really weird branching structure that has /every/
set of credentials in the app repo.

On Monday, February 16, 2015 at 9:50:27 PM UTC-6, Adam Chapman wrote:

I was just about to ask about something very similar…

I’d like to know how to set “Inspect Templates = never” during an
automated cloud instance installation.

@Asher, I use the “Expor settingst to Application.cfc” feature and
configure datasources, mappings etc in there.

Regards,
Adam


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 <javascript:>.
To post to this group, send email to lu...@googlegroups.com <javascript:>
.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/3670f41d-9be4-487f-a36f-c8684fa44556%40googlegroups.com
https://groups.google.com/d/msgid/lucee/3670f41d-9be4-487f-a36f-c8684fa44556%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

The installer uses scripts to set tomcat/nginx ports and whatnot, and
there’s stuff in there for configuring mappings, DSNs, mail servers,
“inspect-template” settings, adding caches, etc. (very little of that is
exposed in the installer itself tho).

The nice thing is that it’s mostly xpath-based, so as elements are added
to the “upstream” configs, they get pulled in automatically.

If you keep the configs themselves in the VCS, you have to keep them in
sync manually. Plus, having the settings abstracted is useful for other
tooling. :slight_smile:

-denOn 2/16/15 3:54 PM, Asher Densmore-Lynn wrote:

Hello,

I’m trying to work out what the best way to configure Lucee is from a
configuration-managment point of view. I’ve got suitable recipes for
installing and configuration Apache, and I can install Lucee and then
put in my own server.xml and web.xml files and configure the connector
myself, that’s not the problem.

But I’d like to configure Lucee itself before I try to boot my
application on it – set passwords, configure mappings and datasources.
So far the “best” way I have to do this is to create an unserved
directory, put a CFADMIN-employing template in it, boot Lucee, call that
template, then delete that template because I don’t especially want
plaintext credentials anywhere they might get served.

It works most of the time, but it seems a little rickety and certainly
it’s not my preference. I have reasons for not wanting to load the app
configuration into Application.cfc. Is there another way to do this I’m
not seeing?


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+unsubscribe@googlegroups.com
mailto:lucee+unsubscribe@googlegroups.com.
To post to this group, send email to lucee@googlegroups.com
mailto:lucee@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/lucee/74a62a28-654a-4e78-bda6-e14f71b556f0%40googlegroups.com
https://groups.google.com/d/msgid/lucee/74a62a28-654a-4e78-bda6-e14f71b556f0%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout.

I use Ansible for provisioning and the only point I can’t do is install
extentions (I need memcached and mongodb).

I’d like to know how to set “Inspect Templates = never” during an
automated cloud instance installation.

You can do this with:

See:

https://bitbucket.org/lucee/lucee/src/5b469e1d52c260ecc8d211871ff52e14f4e84621/lucee-cfml/lucee-admin/admin/server.cache.cfm?at=master

Regards,
David Sedeño