plane icon indicating copy to clipboard operation
plane copied to clipboard

Configurable hostnames for microservices: Non docker-compose based setup

Open rounakdatta opened this issue 1 year ago β€’ 2 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

Summary

Hello, appreciations for the IndiaFOSS 3.0 talk by Aaryan!

I was preparing for self-hosting Plane. I use Hashicorp Nomad for deploying my applications, and hence was starting to structure the Docker Compose as a Nomadfile. From what I could interpret, it seems that the setup is overall assuming the docker-compose service names to be hostnames, and it isn't configurable right now. I understand that it streamlines the setup, but my Nomad setup would require that.

Is it possible that instead of auto-inferring the hostnames, we accept it for each service as an env var?

Why should this be worked on?

For improving the array of deployment techniques.

rounakdatta avatar Oct 29 '23 18:10 rounakdatta

Hello @rounakdatta, I apologize for the delayed response; I overlooked this issue. @manishg3, who manages our DevOps, would be the appropriate person to address your query.

vihar avatar Nov 10 '23 17:11 vihar

@rounakdatta

We are working on creating the non-docker setup. It will be available soon.

mguptahub avatar Dec 20 '23 04:12 mguptahub