Skip to content

ENVAR PORT naming/clash #217

@nomandera

Description

@nomandera

It would appear that both the dashboard and the agent may support an environmental variable simply named PORT.

This can result in issues if the same ENVARS are shared e.g. via a common .env file.

For the avoidance of confusion, clashes and to better fall inline with other variable naming I request that each image allow the use of a unique ENVAR e.g. TRAEFIK_LOG_DASHBOARD_PORT or similar.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions