fix: ldk use info log level by default #517
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
also you should update this file https://getalby.com/install/hub/fly.toml |
|
Thanks @matjaz ! |
rolznz
commented
Aug 21, 2024
Edit: it's not set there, so it'll use the default value from Alby Hub which is fixed in this PR. |
matjaz
reviewed
Aug 21, 2024
| @@ -12,7 +12,7 @@ swap_size_mb = 2048 | |||
|
|
|||
| [env] | |||
| DATABASE_URI = '/data/nwc.db' | |||
| LDK_LOG_LEVEL = '2' | |||
| LDK_LOG_LEVEL = '3' | |||
| LOG_LEVEL = '5' | |||
There was a problem hiding this comment.
@rolznz this should be 4? same as in .env ?
There was a problem hiding this comment.
Info level is the one we want by default, which is 3
There was a problem hiding this comment.
in .env.example LOG_LEVEL is set to 4. in fly it's 5.
There was a problem hiding this comment.
Ah, this has been fixed in master now. Thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DEBUG can cause a lot of spam messages and the log files to get too large.