Configuring Docker Swarm and Exposing Ports: TypeSense Documentation
TLDR gaurav sought assistance on running the '/health URL' and exposing it to port 80 in docker-stack.yml based on TypeSense documentation. Jason explained that different network adapters should be used for each VM.
1
1
1
Oct 18, 2022 (14 months ago)
gaurav
11:44 AMI was trying running docker swarm based on documentation and it worked for me where i was able to set up in multiple AWS VM’s using it.
However this might be a simple question but i am not sure how to run
/health URL as it didnt provided in documentation.Also i want to expose it to port 80, how to do it in
docker-stack.yml ?Again shoutout to TypeSense team and community. 🚀
1
Jason
06:30 PM--api-port in the docker stack config fileJason
06:31 PMYou want to use curl or postman for this
Oct 19, 2022 (14 months ago)
gaurav
11:30 AMSo in multi VM setup. I think for each VM we have to provide different ports, as the docker-stack throws error.
Jason
03:12 PM1
1
Typesense
Indexed 3015 threads (79% resolved)
Similar Threads
Configuring Typesense via Docker and Resolving "Not Found" Error
Pallavi encountered issues while configuring typesense via docker, including a "Not Found" error message. Jason advised to hit the /health endpoint to check the server's health.
Deploying to Fly.io via Dockerfile
andrew asks how to launch to Fly.io with Docker. Jason guides them on the environment setup, specifically mentioning persistent VMs, and approves andrew's Dockerfile setup.
Configuring a Typesense Cluster
Chetan had trouble configuring a Typesense cluster and facing issues with "peering-address". Kishore Nallan advised defaults for network settings, understanding Docker's role in networking, and provided tips for troubleshooting. Issue resolved when Chetan used a specific Docker argument.