Support for private GitHub repositores

[razorblade23]

It would be benefitial to support private GitHub repositories for auto-update option.

This could be perhaps made with embedding GitHub token (read only and scoped to repository)

[bitranox]

store the github token for the private repo in Windows Credential Manager :

Best option for Python on Windows. Windows Credential Manager

• Secrets are encrypted using Windows DPAPI.
• Tied to the current user account.
• Survives reboots.
• No plaintext files.

Store a secret

From PowerShell:

cmdkey /add:MyApp:DB_PASSWORD /user:ignored /pass:SuperSecret123

Read it in Python

Install helper:

pip install keyring

Python:

import keyring

password = keyring.get_password("MyApp", "DB_PASSWORD")

[JeelDobariya38]

what i think

The whole thing of private repository update.. doesn't make sense to me. cuz, for pychrubile app to update (its) user app, need to download or read the private repository of that user on thier user's machine.

to me when i say a repo is private i mean it should not be accessed for read and write.. so, i guess update from private repository doesn't make sense. because user's user will inevitably have a read access.. correct me if i am worng?

where this make sense according to me.

i guess this setup make sense, if you have 5 group of friend how wanna use a common software developed by one or more among them... then i guess it make sense to give them all a token individually, to (read) access github repository... but i guess this will have scalability issue because 5 is okay, 10 is still fine, but 30 or 40 and each individually have token, would be nightmare to handle for developers (pychrubile's user).. you can still divide them into group and make a group token but that make you lose control on individuals...

what i think could be a good solution

if a person wanna have a private code with auto update. then, (according to me) he should be ready to maintain two seperate repository one public and one private... then pychrubile's user (developer) can do there internal development work in a private repo and then push a update to public repository... for pychrubile auto download/update.

this way, the developer could avoid all that token mess and still can do what they want to do... and the developer will not be mislead... because for pychrubile and to some sense python as a whole.. developer should know that here, thier code is not private...

and when developer use auto update they are essential make a thier private repository, public, in way that doesn't show on thier github dashboard. but it is still public in some sense. because with auto update features your repository is publicly readable but still shows private on github dashboard...

Correct me if i am wrong.. or if i am mis-interpreting this feature... but this what i am think... i will happy to hear what you think on my perspective @razorblade23