Running_Bisq_on_Tails at least needs a disclaimer about wiki HOT 13 CLOSED

Hi. I have run into the same problem but I managed to install Bisq on Tails permanently and would like to share a step-by-step guide on this Wiki page for other users to do so.

from wiki.

@amosgroth that's awesome -- people have been asking about that lately! Would you mind posting your guide here?

Then we can get someone with access to the wiki to edit & post it there. We don't provide public edit access to the wiki any more after incidents with spam and abuse.

from wiki.

Thanks, added.

It seems the guide was written with the expectation that the user would set up persistent storage, since it's listed in Preparations.

Anyway I've added a warning to the Install section.

@freimair if there's anything in particular you think could/should be added to help, please do.

from wiki.

from wiki.

@nayfield your are saying that

Do a simple sudo apt install ./[yourbinaryhere]

would be the proper way?

from wiki.

from wiki.

I'd suggest reopening this - the warning doesn't help a tails user unless they want to test things out one time. It all goes away at reboot.

But I do see value of Bisq on tails if done correctly.

I have a feature proposal in tails upstream that they need to commit before this will work ...

But I can see a path to a script that would make bisq work on tails in an 'expected' fashion (e.g. reboot tails and you still have your stuff)

I would need the bisq project to do two things:

1. Provide bisq via an apt repo instead of a dkpg download
2. update the bisq package to install a shell script that never gets run on a normal install

The second item lets bisq upstream be in control of future from an upgrade perspective - the tail install instructions (both steps) would let Bisq change the file that is only used for those who do step 2 and provide an upgrade hook every time a tail install boots.

This is the most sustainable concept I can come up with - if future tails breaks bisq you have a hook to fix the breakage on the next boot once you update your package.

from wiki.

bisq-network/bisq#4563

bisq-network/bisq#4564

If you can re-open this issue I can provide a PR against it once the dependencies are resolved. (two in bisq and one in tails - and I'm proposing to provide the PR for 2 of the 3. I could easily implement the third but I'm not a bisq website admin)

from wiki.

I also think this issue should be re-opened. I just completed the wiki instructions after setting up persistent storage and it does not result in a persistent install. I tested this by rebooting tails and I did not have Bisq installed.

I think in addition to what @nayfield mentioned, wouldn't the default directory for Bisq need to be changed to the Persistent directory on tails?

from wiki.

Here we go:

https://github.com/amosgroth/docs/blob/master/Bisq/Running%20Bisq%20on%20Tails.wt

Since I am not running MediaWiki and I couldn't find a fast way to view the outcome (html), please feel free to try and review.

from wiki.

utACK: https://bisq.wiki/Running_Bisq_on_Tails#Persistent_Data_Directory

from wiki.

I am not finally happy with it. Using the dotfiles works but it seems like Bisq is storing the chain data somewhere else (and Tails deletes them) so Bisq has to synch over and over again after restarts...

from wiki.

Feel free to let me know about possible updates... in any case, all data should still be inside the data directory, there's nowhere else I know of that Bisq saves its data

from wiki.