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

Open
erdnussflips opened this Issue Mar 16, 2015 · 19 comments

Comments

Projects
None yet
9 participants
@erdnussflips
Copy link

erdnussflips commented Mar 16, 2015

Let the users decide, whether they will use it in normal mode or portable mode.

In portable mode:

  • saves all data from Roaming folder (Windows) in execute folder (where the *.exe or *.jar is located)
  • maybe the auto unlocking feature #40 should not be available here

One solution could be the Portable Apps Platform App Maker, but a real portable mode of the application is much better

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Mar 16, 2015

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.

@overheadhunter overheadhunter added this to the v0.7 milestone May 7, 2015

overheadhunter added a commit that referenced this issue May 10, 2015

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented May 24, 2015

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.

@overheadhunter overheadhunter removed this from the v0.7 milestone May 24, 2015

@tobihagemann

This comment has been minimized.

Copy link
Member

tobihagemann commented Aug 26, 2015

#26 seems to be fixed, so how about plans on moving forward with this issue?

@jaorueta

This comment has been minimized.

Copy link

jaorueta commented Nov 3, 2015

criptomator.jar is not executable with 'java -jar'?

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Nov 3, 2015

@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.

@markuskreusch markuskreusch added this to the 1.x milestone Feb 26, 2016

@markuskreusch markuskreusch self-assigned this Apr 5, 2016

@markuskreusch

This comment has been minimized.

Copy link
Contributor

markuskreusch commented Apr 28, 2016

A portable version can not rely on FUSE / Dokany beeing installed so after #252 and #207 we will need to allow a "WebDAV mode" or the user has to install dokany / fuse to allow usage of a portable version.

@tobihagemann

This comment has been minimized.

Copy link
Member

tobihagemann commented Jun 15, 2016

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?

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Jun 15, 2016

@MuscleRumble: Depends on #267

@tobihagemann

This comment has been minimized.

Copy link
Member

tobihagemann commented Jun 15, 2016

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.

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Jun 15, 2016

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.

@spbriggs

This comment has been minimized.

Copy link

spbriggs commented Oct 19, 2016

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/

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Oct 19, 2016

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.

@spbriggs

This comment has been minimized.

Copy link

spbriggs commented Oct 19, 2016

Thanks @overheadhunter. I'll take a look into your suggestion.

@capstan1

This comment has been minimized.

Copy link

capstan1 commented Nov 9, 2016

@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?

@capstan1

This comment has been minimized.

Copy link

capstan1 commented Nov 9, 2016

Think I resolved what I needed with this simple batch-file:

@echo off 
%~dp0\PortableApps\JavaPortableLauncher\JavaPortableLauncher.exe %~dp0\PortableApps\Cryptomator-1.2.0.jar
@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Dec 5, 2016

Might be valuable if we wish to distinguish installation types: InnoSetup Documentation

@isipka

This comment has been minimized.

Copy link

isipka commented Nov 7, 2018

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/

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 ?

@AnaranBluto

This comment has been minimized.

Copy link

AnaranBluto commented Nov 7, 2018

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/

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.

@overheadhunter

This comment has been minimized.

Copy link
Member

overheadhunter commented Nov 9, 2018

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 ?

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.

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