normally script my builds, but span up a docker nginx lucee container on my local windows docker... port 80 works fine... lucee/lucee:6.1.0.230-SNAPSHOT-nginx-tomcat9.0-jdk11-temurin-jammy 1. where do i get passwords for logging into os so i can configure it? 2. cant get admin so assuming it's firewalled off... even on localhost docker?? am i missing something. (set cfadmin password through env var)

"passwords for logging in to OS"?

on the docker container... assuming ubuntu?

A container is just for running a process. That it needs to have an OS there to facilitate this is kinda coincidental. It's not a VM.

so how to do configure the nginx websites?

so how to do configure the nginx websites?

Same way you normally do, via Nginx's config files. The OS in the container has nothing to do with it, same as it has nothing to do with it on an on-metal installation.

how do i get to the nginx config add new sites? as more and more will be added to this over time? I know how to do this in a vm, or on bare metal

This repo - although PHP not Lucee - should point you in the right dir. https://github.com/adamcameron/php8/blob/main/docker/nginx/Dockerfile#L3 The image will come with a default config set up. Look at the docs for the image on Docker Hub (which are likely incomplete knowing Lucee) If if you - for example - want yer nginx.conf to have something non-std in it... stick a replacement in when you build the image. It's too late by the time you have container. The config is already done and containers are transient by design.

Thanks for that... yeah seeing a lot of that... just seems a weird way to configure it.

You're completely missing the starting li ne and attempting to join the process at a place that just isn't compatible. Your configuration is required before the container even starts.

as for lucee admin no idea why i can't see that out of the box.

So you need to store the details somewhere else, then. Like a dB. Or a flat file... or in a config.json then as part of your new site routine you save the necessary details. And copy them external to the container. So when you start a new container the configuration is already ready.

Appreciate the help. is a bit of Mindshift (like using apple when you've used android)... some of the things you mention i'm already doing so maybe the jump isn't so big.

Start with the realisation that a running container promises you nothing other than to crash and fail... so save nothing you need to keep in the container, ever.

you need configuration in it, just seems they've thought of the hardest way to configure a machine and went 'that sounds great'

it cant be this hard

It isn't hard. You're making it hard on yerself by not learning how the tool works and is intended to be used before declaring it's difficult. That's just a shit way of going about things. It's also no small amount of hubris on your part to declare a widely-adopted ubiquitous industry standard approach as shit cos you don't bother to understand it. The fundamental thing you are missing - willfully, really, because you're ignoring the guidance - is that one doesn't spin up a container and then configure it. One configures an image and then spin up a container based on the definition provided by the image. Containers are disposable. By design. It's the image that is the persisted (and accordingly what you configure).

I read about half way through this, but really its as simple as changing a flag in your docker file to be able to access the Lucee admin. As for nginx config….spin up another container configured for your other site(s) and prep the config for that. Basic fundamentals of Docker…1 container=1 app/site.

TBH I'd run with one container one service. Where in your scenario Nginx is the service. I'd have no worries serving multiple tenants for the same backend multi-tenant app via one Nginx service. But even that is a few steps ahead of where Chris is at, atm

It sounded to me like he wanted it for his local dev environment and to be easily able to add various apps sitting behind an nginx server. TBH tho, I would just spin up commandboxs for whatever app/site I am working on.

Whether it's a commandbox-based image or the native Lucee one, the considerations are the same though aren't they? One still needs to understand how Docker works.

Agree completely, needs to watch a few videos and comprehend how Docker works and common best practices for using it.

From https://hub.docker.com/r/lucee/lucee:

The NGINX tagged Docker images are configured to deny access to the Lucee Admin by default in the default.conf.

Whilst it would be dead handy to also include exactly how to re-enable it, I presume it's obvious if one just looks at the file. I'm on my phone right now so can't really check.

Appears just needing to set

LUCEE_ADMIN_PASSWORD

as an env variable

I presume it's got a commented-out

location

entry pointing to it.

@dawesi You might want to takea. quick look at https://github.com/kukielp/Amazon-SQS-Lucee-CFML It's a little outdates but shows how you can inject into your containers nginx conf files and use docker compose for local dev. It's some early version of Lucee as I havnt updated for a logn time but I think it might still work