You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be incredibly useful if there were a way to run Topgrade in a fully unattended mode.
Currently, setting:
assume_yes = true
in the configuration file will handle most confirmation prompts by automatically responding with "yes." However, the process still stops to request a password for updates requiring admin access.
This presents a challenge, particularly for non-technical users. My goal is to integrate Topgrade into a simple GUI updater. In this application:
Updates can be delayed automatically if fullscreen applications are open.
If ignored for too long, the updater would eventually push itself into view to ensure the system gets updated.
This approach is designed to maintain an up-to-date system with minimal user interaction. However, the current behavior—requiring a password—creates a significant roadblock for non-technical users, as they often have no idea how to handle such prompts.
Running Topgrade directly with sudo is not a practical solution, as highlighted in Discussion #825.
If there’s a way to address this issue—whether it’s through existing configuration options, new features, or external integrations—I’d greatly appreciate any suggestions. For example, securely pre-caching sudo credentials without manual intervention could help.
Adding functionality for a fully unattended mode in Topgrade would greatly enhance its usability for non-technical users and make it an even more powerful tool for keeping systems updated effortlessly.
Thank you for your time and consideration!
The text was updated successfully, but these errors were encountered:
It would be incredibly useful if there were a way to run Topgrade in a fully unattended mode.
Currently, setting:
assume_yes = true
in the configuration file will handle most confirmation prompts by automatically responding with "yes." However, the process still stops to request a password for updates requiring admin access.
This presents a challenge, particularly for non-technical users. My goal is to integrate Topgrade into a simple GUI updater. In this application:
This approach is designed to maintain an up-to-date system with minimal user interaction. However, the current behavior—requiring a password—creates a significant roadblock for non-technical users, as they often have no idea how to handle such prompts.
Running Topgrade directly with
sudo
is not a practical solution, as highlighted in Discussion #825.If there’s a way to address this issue—whether it’s through existing configuration options, new features, or external integrations—I’d greatly appreciate any suggestions. For example, securely pre-caching
sudo
credentials without manual intervention could help.Adding functionality for a fully unattended mode in Topgrade would greatly enhance its usability for non-technical users and make it an even more powerful tool for keeping systems updated effortlessly.
Thank you for your time and consideration!
The text was updated successfully, but these errors were encountered: