-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Configuration example using Docker #1
Comments
So, we updated the compose file adding the following: typesense:
image: typesense/typesense:27.0
environment:
TYPESENSE_API_KEY: typesense-api-key
TYPESENSE_DATA_DIR: /data
#ports:
# - "8108:8108"
volumes:
- typesense_data:/data
networks:
- medusa-network
deploy:
replicas: 3 # Number of Typesense nodes for high availability
placement:
constraints: [node.role == manager]
volumes:
postgres_data:
typesense_data:
networks:
medusa-network:
driver: bridge And:
But it gives up an error in the first node:
Is it normal? |
We tried adding
Yet it does not work. Could it be related to this issue? |
It was checked with But it does not work: Request #1727294949320: Request to Node 0 failed due to "ENOTFOUND getaddrinfo ENOTFOUND typesense"
⠸ Initializing plugins
Request #1727294949320: Request to Node 0 failed due to "ENOTFOUND getaddrinfo ENOTFOUND typesense" We think it is related to the Typesense. |
Finally, passing the ip itself does fix the issue: |
Installing and configuring the plugin is easy, but we want to test it properly using Docker for Typesense.
Right now we have the following compose file:
And we are setting up with the following
.env
variables:We are not sure about this.
Could you help us?
The text was updated successfully, but these errors were encountered: