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

Support for updates using git #3215

Open
Noriller opened this issue May 18, 2023 · 3 comments
Open

Support for updates using git #3215

Noriller opened this issue May 18, 2023 · 3 comments

Comments

@Noriller
Copy link

Noriller commented May 18, 2023

I'm in WSL and I have to update with the offline instructions because of proxy problems, but some CLI applications I use inside wsl have scripts that just clone using git and that works fine.
So, the no automatic install could have an option for updates through git and I think it would solve my proxy problems.

Would this be something possible?

@smcenlly
Copy link
Member

Thanks for your suggestion. I'm marking as a feature request.

I'm wondering why git works from your WSL instance but our update mechanism does not? Does curl or wget allow you to connect to external websites from your WSL instance? If so, we could help you script the update another way. Does Wallaby automatically update on your desktop (outside of WSL)?

Please 👍 the first comment to +1 the issue. If we get enough interest, we'll consider adding the feature in the future.

@Noriller
Copy link
Author

Noriller commented May 19, 2023

So, on Windows I have one proxy (no user/pass and it didn't work)
On WSL, I have to use another proxy (user/pass) and if I set the proxy then it worked this time (not sure if automatically, since I had to use force core update).

I usually can't leave the proxy option in vscode, so when it starts it gets an error and breaks the install.
Those proxies are actually different and somethings they block.

Perhaps it would be possible to "rollback" the installation if it fails for some reason? (or at least check if the downloads were successful before probably deleting the folders?)

@smcenlly
Copy link
Member

In your case, if you're having problem with proxies, I think you're going to have to stick to manual offline installation. The only suggestion we have for you at this point is to try and script as much of it as possible for yourself (depending on when proxy issues become a problem). You may do the same for updates/upgrades.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants