[BUG] Flyteconsole has hardcoded port

[RRap0so]

Describe the bug

Since we've updated Flyteconsole, we're unable to set the port we want. We found that this had become hardcoded into flyteconsole with the recent changes.

Expected behavior

We should be able to pick the port we want by setting the PORT env variable.

Additional context to reproduce

Set the PORT env to other than 8080 and run the docker image. It will always use 8080

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

To address the issue of the hardcoded port in Flyteconsole, it's important to note that the demo cluster's UI port is hardcoded to 30080, as discussed in the forum. This behavior is due to the message in the command line being hardcoded, even though the actual port configuration might be different. For a custom port configuration, changes in the Flyte repository and Dockerfile are necessary, as detailed in the same discussion.

Would you like more detailed steps on how to modify the Flyte repository and Dockerfile to use a custom port?

Sources:

• How should I run the demo cluster if I want to have the flyt
• Hi guys was trying to follow instructions from https docs f

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!