I’m not sure if I should comment here or the ticket because it is tangentially related. What about the LUCEE_ADMIN_PASSWORD env variable? Having LUCEE_ADMIN_PASSWORD set in an .env file doesn’t get picked up (just tried it), presumably because of the same reason the LUCEE_INSPECT_TEMPLATE doesn’t - hierarchy. I don’t want the password saved in plain text anywhere, obviously, so where is the best place to have the password set?
It looks like the .CFConfig.json sets a hspw which is a hashed password. Do I leave that in source control? Or do I use something like "hspw":"{env:LUCEE_ADMIN_PASSWORD}" but have to keep the hashed value in the .env variable? (So then no one will know what it actually is if they need it?)
I’m probably being dumb here, ha. Just wondering the best way to go about the Lucee Admin password.
2 posts - 2 participants
