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

Configuration keys not documented #1596

Open
findurance opened this issue Oct 31, 2024 · 2 comments
Open

Configuration keys not documented #1596

findurance opened this issue Oct 31, 2024 · 2 comments

Comments

@findurance
Copy link

At the moment there seems to be no way for a user to easily find out what kind of configuration options Distrobox has available
The web page at https://distrobox.it/#configure-distrobox only offers a very short example file, with what I guess is only a very limited subset of configuration keys available.

At minimun, there should be a reference / link, where all the config keys are defined. Even better if there would be a template config file, with documented keys, and a user can place to his system after editing. And even better if the documentation would be online.

For example, I recently learned that there is a assume_yes key, but that is not documented anywhere.

@findurance
Copy link
Author

findurance commented Nov 25, 2024

In this comment, for example, assume_yes is referenced, which could be set to avoid unwanted actions.

This is a problem with your distro's configuration not with distrobox
As you already see it does not forcibly do anything if the config to assume_yes is not set

But I cannot seem to set that anywhere, so it seems impossible to configure such thing at all. Nor do I find any reference of any assume_yes key usage in Distrobox scripts:

Going through distrobox-create and distrobox-enter scripts, there seems to be no such key even in the code. The prompt phase in the distrobox-enter seems to not refer to such configuration key either.

So I'm curious where do the configurations come from, does any script actually use such, or was that just false information?

@findurance
Copy link
Author

There's a possibility for a rather clumsy workaround, but this requires meddling with the backend system command, so it's not working on Distrobox level:

if podman container exists "${containername}"; then
    distrobox enter "${containername}"
fi

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

No branches or pull requests

1 participant