Skip to content

Commit

Permalink
ELK+UIUC_CM slightly works
Browse files Browse the repository at this point in the history
With this version of the docker-compose.yml, all the UIUC containers
come up, and the two ELK containers come up as well.  With this
configuration I was able to log into the elasticsearch container and
at least start the password setup utility.

So I'm not going to say that it's *working*, but as far as elk is
concnered it works at least as far as ELK ever has at NCSA.
  • Loading branch information
craigsteffen committed Dec 12, 2024
1 parent de4960d commit 83644d6
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -98,9 +98,9 @@ services:
image: rabbitmq:3.13-management
hostname: rabbitmq
restart: unless-stopped
profiles:
- cdrhook
- allinone
# profiles:
# - cdrhook
# - allinone
environment:
RABBITMQ_DEFAULT_USER: "${RABBITMQ_USERNAME:-guest}"
RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASSWORD:-guest}"
Expand All @@ -115,16 +115,16 @@ services:
image: ncsa/criticalmaas-cdr:${CDRHOOK_VERSION:-latest}
hostname: cdrhook
restart: unless-stopped
profiles:
- cdrhook
- allinone
# profiles:
# - cdrhook
# - allinone
depends_on:
- rabbitmq
environment:
# CDR_URL: "${CDR_URL}"
CDR_TOKEN: "${CDR_TOKEN}"
CDR_KEEP_EVENT: "no"
#CALLBACK_URL: "${CALLBACK_URL}"
# CALLBACK_URL: "${CALLBACK_URL}"
CALLBACK_URL: "https://${SERVER_NAME}/cdr"
CALLBACK_SECRET: "${CALLBACK_SECRET}"
CALLBACK_USERNAME: "${CALLBACK_USERNAME}"
Expand All @@ -145,9 +145,9 @@ services:
hostname: monitor
build: monitor
restart: unless-stopped
profiles:
- cdrhook
- allinone
# profiles:
# - cdrhook
# - allinone
depends_on:
- rabbitmq
environment:
Expand Down

0 comments on commit 83644d6

Please sign in to comment.