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
add portable mode #48
Comments
Nice idea. Should be easy, as Cryptomator only writes one single configuration file (containing the items of the vault list). This should be a separate download though to keep the app-internal configuration simple. |
As we're depending on .net runtime libraries (see #26) in the native build (known issue in JavaFX), we have to wait for an upstream fix. Deferring portable mode to a later version. |
#26 seems to be fixed, so how about plans on moving forward with this issue? |
criptomator.jar is not executable with 'java -jar'? |
@jaorueta in a portable setup we can not rely on a JVM being installed. Anyway as we "bring our own JVM" it is still possible to start Cryptomator from a external drive, we just haven't tested it yet. |
Just found out that WebDAV might also cause problems, when using Cryptomator only in user space. The installer and the application modify the registry. I'm not sure if the modifications are absolutely necessary, but can we even offer a portable version? |
@MuscleRumble: Depends on #267 |
But not only that, right? The installer also modifies the registry: https://github.com/cryptomator/cryptomator-win/blob/master/package/windows/Cryptomator.iss#L41 With a missing installer I'm not sure if Cryptomator is usable, when these modifications aren't executed. 😅 Just wanted to document this in this issue to keep this in consideration for a portable version. |
We don't need the registry stuff done by the installer. It just increases the file size limit of the Windows WebDAV client. Neither do we depend on the reg changes done at runtime. Both are just attempts to make Windows suck less. |
Hi all. You might be interested to know that I've managed to get Cryptomator to run from a memory stick using the .jar file and Portable Apps' jPortable. I'd welcome feedback from anyone who's able to test it. Details here https://www.simonpbriggs.co.uk/cryptomator-portable-usb-stick/ |
Hi @spbriggs, great work! What might be interesting is the possibility to pass arguments like the settings path or the log file path to the jar file. Using a .bat script to start up the Java program you should be able to further customize Cryptomator's behavior. |
Thanks @overheadhunter. I'll take a look into your suggestion. |
@spbriggs Cryptomator works perfect on my thumbdrive now! That was right, what I was looking for (having sensitive data travelling from work to home). Thank you very much. I would also appreciate an easier way of starting it. Like anShortcut to start Cryptomator directly (without opening portableApps-Platform->jPortable Launcher -> choose Cryptomator). Would that be possible? |
Think I resolved what I needed with this simple batch-file:
|
Might be valuable if we wish to distinguish installation types: InnoSetup Documentation |
New version 1.4.0. jar is compiled with Java class file version 53.0, jPortable suports class file versions up to 52.0 :( so workaround won't work with unless Java 10 is installed locally. Any solution for this ? |
I hope for a solution as well. version 3.5 works but not version 4.0. A Portable Cryptomator would be a wonderful thing. |
We can not move back to Java 8. This is technically outdated and we're already using new language features. I am sure, that Portable Apps will support OpenJDK 11 in the near future (after all Java 11 is a LTS version). However, we don't support Java 11 yet. 🙁 We will move to it as soon as possible, though. Until then, please understand, that Cryptomator 1.4.0 doesn't provide any real benefit to portable installation, since this release is all about FUSE and Dokany. Neither of which can be used without installing kernel modules, which would defy the purpose of Portable Apps. So if you want to use a portable edition, please keep using 1.3.x for now. Its vaults are 100% compatible to 1.4.0. |
Any news on this feature request ? |
Nice job! Thanks for sharing! |
I've just tried this and it failed – does the Java incompatibility mean that this method doesn't work at all, at present? If the answer's no, maybe someone knows what I did wrong: In particular, I followed the instructions and downloaded buildkit-win.zip. I'm not sure whether that's the right file. Anyway, I unpacked it and ran launcher-win.bat. This is the step where it failed, i.e. it opens a cmd window for only a second and nothing happens. |
With 1.5.0 having broken backwards compatibility to the working portable jar an official portable mode implementation becomes much more important again. |
I'd like to stress @Protarios point. Having Desktop, Android and iOS on Version 1.5.x now, I would love to migrate my vaults to vault format 7. However, I regularily need access to my vaults from windows machines I do not have admin privilidges on. That only works with the old portable jar not supporting vault format 7. So please consider adding portable support or at least some kind of workaround solution for technically apt users. Thanks! |
Actually, since version 1.4.12 we already release portable versions. Download the buildkit for the targeted os, unpack it and start Cryptomator with the containing @overheadhunter I think this can be closed. |
Thanks for the quick response, @infeo. Keep up the good work in Bonn, and greetings from Beuel :) |
I don't think that using the buildkit hits the core of this issue. After all it still requires a JRE and just barely provides the same user experience. But I agree it is a viable workaround for now. |
For Linux we already release a portable solution, since the appimage format is portable by desgin. The more interesting question is, if the settings/logs/etc. paths should be adjusted or not. |
@infeo Writing data in another directory for portable release doesn't make sense. |
Looking into the launcher-win.bat, it seems like settings and Log could rather easily be stored/configured to be stored on the executable folder
But even apart from that, the solution to take the build-kit and bundle it with a Java14 RE works fine for my needs to be able to run it on a windows machine where I do not have administrator privileges. Thank you for that. You really earned me getting my "awesome people"-certificate :) |
Cryptomator is available through Portapps if you want to try it: https://portapps.io/app/cryptomator-portable/ |
@crazy-max this is awesome! It is unofficial but maybe a note in the readme could be added ? 🤔 |
Agree, good job @crazy-max ! |
It's also possible to make it works with AdoptOpenJDK and the buildkit. Here the bat file I use to run Cryptomator from my USB key : |
I use this portable version now and then , but it usually is many versions behind current. I appreciate that this portable version exists at all - everything takes work and time. |
As a hack, is there a way to install the portable version and then, for example, simply move one (jar?) or a few files from the official installation into the portable app directory....thus essentially upgrading the portable to current? |
If you are working with Windows you can do the following:
You can copy some jar files from it or you can use it complete as portable Package. |
Let the users decide, whether they will use it in normal mode or portable mode.
In portable mode:
One solution could be the Portable Apps Platform App Maker, but a real portable mode of the application is much better
The text was updated successfully, but these errors were encountered: