cloudant-change-listener README clarification

[RogerSnook]

Maybe it's me or perhaps the Console UI changed, but I'm having trouble with the cloudant-change-listener in simply just picking up the _changes to my Cloudant DB. Can someone please revisit this README?

[RogerSnook]

Update/further information: I'm getting the error below when I submit the job. It's like it can't find the job.mjs in the dockerfile:
ENTRYPOINT ["./cloudant-change-listener/job/job.mjs"]
(and I've tried without any directory and with the job directory).

StartError : container 'appvestr-cloudant-watcher' exiting with: 128/failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "./cloudant-change-listener/job/job.mjs": stat ./cloudant-change-listener/job/job.mjs: no such file or directory: unknown

[RogerSnook]

@jeremiaswerner - following up to my LinkedIn messages, I had success changing the cloudant-change-listener/Dockerfile ENTRYPOINT to CMD and this successfully launched the daemon. In the same file, I also updated FROM gcr.io/distroless/nodejs22-debian12. These env vars were all required from the README:

CE_DB_NAME (the cloudant database name to watch)
DB_NAME (seems like a dup, but the same cloudant database name to watch)
CE_API_KEY (created in IAM for the CE service)
CE_TARGET (my function URL)
DB_LAST_SEQ "now"
CE_SERVICES (Key reference | Secret: ce-services, key: myjobname)
CE_REGION (where my ce project resides)
CE_PROJECT_ID (from the GUID of the project)
CE_API_BASE_URL (from CE)

[reggeenr]

Thanks for pointing this out. We adjusted the Dockerfile as you suggested and verified that it is working as expected. See #328