blender-addon-updater
blender-addon-updater copied to clipboard
CGCookie
Error due to creating folders without permission
As referenced in this issue on CrowdMaster, it seems sometimes windows users run into an issue if they don't have the right permissions and if the updater path doesn't already exist.
Recommendation: Developers should always pre-include/pre-create the updater folder or perhaps look into a different method to create folders that doesn't do absolute paths. https://github.com/johnroper100/CrowdMaster/issues/57#issuecomment-319743123
Issue also referenced here, will be updating documentation / tutorial to address the issue. https://github.com/ndee85/coa_tools/issues/81
In a studio setting it's not desirable that users update their software or plug-ins, as this would quickly cause issues with multiple users using different versions of software while working on the same project. This is why sysadmins at studios generally install software as read-only and don't give users admin/root access. So the workaround suggested won't really work in this situation.
A better solution would be to have the addon-updater fail gracefully if it can't create folders, and allow the plug-in that's using it to load even if the updater can't run.
Also note that many medium to large studios have to follow strict security requirements under TPN, which, in addition to not giving users local admin rights, includes that workstations should not have internet access.
Thanks for the comment. As I would interpret it, I would say the addon updater indeed fails gracefully - if an error occurs, the already installed version of the addon is still useable. On TPN, if there is no internet activity, the updater will by design not work (unless you developed an extension to include a "local" engine which pulls updates from say a shared network folder or something).
Sample no internet message; the rest of the addon remains useable.
Based on what you describe, it sounds like no addon self-updaters would be able to work (by design) with TPN anyways, but if you are a studio admin and have some ideas, I would be open to hearing how we could better accommodate. It sounds like something you would rather manage centrally rather via within individual addons though. Let me know if you are seeing something different from the above!