-
Notifications
You must be signed in to change notification settings - Fork 31
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
(refactor): startapp.sh script #110
Conversation
HEy @xela1 |
This is missing in the section where it installs the client if it doesn't already exist, so I just added cd /tmp, but I can alter that backblaze-personal-wine-container/startapp.sh Lines 152 to 153 in 615dd05
Whereas it exists in the update code backblaze-personal-wine-container/startapp.sh Lines 79 to 80 in 615dd05
Thinking about it more, is there a reason why it doesn't just call the fetch_and_install if there is no current installed client? I have a few 'enhancements' I've being playing with that I'm happy to run past you before I raise a PR for them
|
Hey!
|
|
Hey, |
The exe help shows the parameters, but I'll leave this for now. I'll submit a PR tomorrow for the other bits for you to review |
I agree and I am also concerned about 2FA support on the silent install. If accounts with OTP don't work, that would not be acceptable. |
I think Backblaze recognizes drives by a file it writes on the filesystem on the disk. So I think re-adding symlinks would not hurt, but testing of that would be needed. |
Good point, hadn't thought of this, I'll see how it behaves |
It doesn't seem to like the drive letter being changed, the original drive shows as unplugged and doesn't show as the new letter, but when reverted to the original letter it recovers fine. Adding new disks (following the /drive_x pattern) are in the backblaze client to be selected on the first container startup after adding, no need to restart the container after symlink |
I asked Backblaze support a 2nd time about this, and they mentioned that this silent install is - even with the exe installer - only available with groupID and group token and will misbehave when those parameters are missing. |
Volume ID and drive letter are "married" for Backblaze. If it sees the drive "X" with a different volume ID it's unplugged for Backblaze. Adding new symlinks for new mounts is good 👍 |
I mean they're incorrect, as it works and has options to do it without the groupID etc, but I'm really not bothered enough to push for this, it was just a nice to have on my list where we can remove as much user interaction as possible |
I pushed my latest commits into the PR last night which contains the refactoring of the update code, the initialization of wine and the auto-symlinking of mounted volumes. I've tested this in every way I can think possible, but would appreciate someone else performing some testing Wine Initialization
Symlinking
Install/Updating
|
Thanks @xela1 for your work. To me this seems to meet the quality requirements for a merge, but I will leave the final decision of that to @traktuner because he originally wrote the update code. Also the new symlinking functionality requires the README to be changed: The unnecessary step(s) in the install process, that are now automated should be removed and new advisories on how to handle the drive letters, like you have already outlined above are needed. It would be nice of you to add these readme changes to the PR :) |
Yes, I was thinking that earlier, I'll work on that when I finish work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM ;)
Thank you for working on this and the improvements!
Found a few issues with this if someone wants to confirm