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

General/sitewide bleachbit.ini file? #1350

Open
marcogaio opened this issue Mar 15, 2022 · 2 comments
Open

General/sitewide bleachbit.ini file? #1350

marcogaio opened this issue Mar 15, 2022 · 2 comments

Comments

@marcogaio
Copy link

I've looked in docs and a bit also in the code, but i've not found an answer. I'm speaking particularly on running bleachbit on windows.

There's some way to have a general/sitewide blechbit.ini config file, so some option can be predefined for users, or (better?) also forced for users?

I surely can use https://en.wikipedia.org/wiki/Active_Setup to manage some predefine options for users, but... i ask here if there are better method.

Thanks.

@az0
Copy link
Member

az0 commented Apr 5, 2022

As of BleachBit 4.4.2 there is no such option. For Active Setup, I assume you would copy the bleachbit.ini file into the user's directory if the file doesn't already exist.

I'm interested in what enterprise users need for mass deployments, so let me know more about what you're thinking. For example, what would you like to pre-define or force?

@marcogaio
Copy link
Author

As of BleachBit 4.4.2 there is no such option. For Active Setup, I assume you would copy the bleachbit.ini file into the user's directory if the file doesn't already exist.

Exactly.

I'm interested in what enterprise users need for mass deployments, so let me know more about what you're thinking. For example, what would you like to pre-define or force?

Generally we need:

  1. silent options for installation, and seems here we are OK.
  2. options or tools for disable auto-update or at least manage the update: generally a sysadmin manage also the update of various tools installed on the fleet
  3. Configuration on behalf of user, typically:
  • preset some options for users, so the software came decently configured, but users can modify the configuration; configuration can be a default conf, that users copy on first run, or options that users can override; clearly second options is better, because sysadmin can change some default and have applied to users, if they have not specifically overrided it.
  • lock some options for users, eg users cannot modify them.

Looking at bleachbit, the best way seems to me to have an sitewide bleachbit.ini that can define and/or lock global options for users.

Thanks

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

2 participants