Skip to content
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.

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

Kolibri debug take 2 #127

Merged
merged 2 commits into from
Nov 13, 2023
Merged

Kolibri debug take 2 #127

merged 2 commits into from
Nov 13, 2023

Conversation

dbnicholson
Copy link
Member

After testing, I found the proper way to get the environment variables set for the daemon is flatpak override. While here again, I decided to add support for KOLIBRI_DEBUG_LOG_DATABASE.

See: #123

Since the Kolibri daemon process is D-Bus activated, it won't inherit
the environment passed from `flatpak run --env`. Instead, the
environment variable can be set from a flatpak override where it will be
picked up when the service is launched via `flatpak run`.
Like the `KOLIBRI_DEBUG` environment variable, use the
`KOLIBRI_DEBUG_LOG_DATABASE` environment variable to set the
`debug_database` value passed to the Kolibri initialization routine.
This is also how `kolibri start` works. Any other Kolibri options can be
handled normally.
Copy link
Contributor

@manuq manuq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that's the way to go with flatpak and environment variables. Thanks for documenting it and adding an option for the database debugging.

@manuq manuq merged commit 00ff7a5 into main Nov 13, 2023
2 checks passed
@manuq manuq deleted the kolibri-debug-take2 branch November 13, 2023 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants