[Feature] Maybe the password in docker-compose.yaml can be random rather than 123456?

[baalchina]

Feature Request

Hi, I had installed hertzbeat with docker compose, ref to :https://hertzbeat.apache.org/zh-cn/docs/start/docker-compose-deploy

But I found that the PostgreSQL username and password used by Hertzbeat are root/123456. That doesn't seem like a good idea in a production environment. After installed hertzbeat, I used db tools to connect my server with root/123456, and everything in hertzbeat shows.

Maybe something can be done? A random password, or using .env, or anything else.

Thanks

Is your feature request related to a problem? Please describe

No response

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response

[Bhavya-Sonigra]

Hi, I'd like to work on this issue if it's still open. Planning to either randomize the default password or move to .env-based config — will confirm approach once I look at the current docker-compose setup.

[Bhavya-Sonigra]

Hi, I'd like to work on this issue if it's still open. Planning to either randomize the default password or move to .env-based config — will confirm approach once I look at the current docker-compose setup.

To scope this properly — would you prefer a minimal fix (just add a comment/warning in the compose file about changing the default password before production use) or the fuller fix (move to .env-based config so the password is configurable and consistent across docker-compose.yaml and application.yml)? Happy to go either direction, just want to align before implementing.

[baalchina]

Hi Bhavya,I think the best approach is to randomly generate a strong password and output it to the user in the installation logs. If that's too complicated, we can remind the user to edit the env file first, let them set their own password, and then run docker compose up.

Just my two cents—thanks!