New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[REQUEST] Better show where all the configuration should go #141

Open

2 tasks

Giszmo opened this issue Jan 16, 2023 · 1 comment

Open

2 tasks

[REQUEST] Better show where all the configuration should go #141

Giszmo opened this issue Jan 16, 2023 · 1 comment

Assignees

Labels

Giszmo commented Jan 16, 2023

Pledge

I'd offer $20 in BTC or LN for this but it would help others much more than myself who already found stuff the hard way.

Is your feature request related to a problem? Please describe.

The relay hitting limits doesn't communicate well what's limiting it and which config to touch to fix that.

Describe the solution you'd like

At startup, the relay should log out all the config files it is considering and using. If configs get merged, it should show the list and indicate which config overwrites which.
When hitting limits it should hint at what to do. "db FATAL: sorry, too many clients already. Try increasing configs A, B and C inside the project folder's config files D, E and F if using docker. ..."

Giszmo added the enhancement label

Giszmo assigned cameri

Owner

cameri commented Jan 17, 2023

Should have split this into two requests because one is a feature and the other one is a bug fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment