Skip to content
This repository has been archived by the owner on Dec 13, 2023. It is now read-only.

Commit

Permalink
Attempt fix for redis connection
Browse files Browse the repository at this point in the history
  • Loading branch information
karczewsky committed Mar 19, 2023
1 parent 8c65ec1 commit 20eab6d
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 12 deletions.
11 changes: 0 additions & 11 deletions docker/docker-compose.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,6 @@ services:
build:
context: ../
dockerfile: docker/server/Dockerfile
networks:
- internal
ports:
- 8080:8080
healthcheck:
Expand Down Expand Up @@ -43,12 +41,8 @@ services:
build:
context: ../
dockerfile: docker/ui/Dockerfile
networks:
- internal
ports:
- 5000:5000
links:
- conductor-server
stdin_open: true

redis:
Expand All @@ -70,8 +64,6 @@ services:
- xpack.security.enabled=false
volumes:
- esdata-conductor:/usr/share/elasticsearch/data
networks:
- internal
ports:
- 9200:9200
- 9300:9300
Expand Down Expand Up @@ -107,6 +99,3 @@ services:
volumes:
esdata-conductor:
driver: local

networks:
internal:
2 changes: 1 addition & 1 deletion docker/server/config/config-local.properties
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ conductor.db.type=redis_standalone

# Dynomite Cluster details.
# format is host:port:rack separated by semicolon
conductor.redis.hosts=rs:63709:us-east-1c
conductor.redis.hosts=rs:6379:us-east-1c

# Namespace for the keys stored in Dynomite/Redis
conductor.redis.workflowNamespacePrefix=conductor
Expand Down

0 comments on commit 20eab6d

Please sign in to comment.