From @Mithgol on Tue Sep 15 2015 11:02:05 GMT+0000 (UTC)
A portable application is the one that is designed to run on a compatible computer without being installed in a way that modifies the computer’s configuration information. Such application can be stored on any storage device (including internal mass storage and external storage such as USB drives) – storing its program files and any configuration information and data on that storage medium alone.
I imagine some users would want to have the same local storage (and pinned media) at home and at work by bringing a mere USB stick where full BYOD is not practical.
Copied from original issue: https://github.com/ipfs/faq/issues/33
From @whyrusleeping on Tue Sep 15 2015 14:44:39 GMT+0000 (UTC)
go statically compiles by default, an ipfs binary should run on any compatible system.
We provide prebuilt binaries here: https://gobuilder.me/github.com/jbenet/go-ipfs/cmd/ipfs
From @Mithgol on Tue Sep 15 2015 14:49:59 GMT+0000 (UTC)
And where is the application’s local storage created? (I haven’t yet tried the prebuild binary; the answer may become obvious when I try.)
From @whyrusleeping on Tue Sep 15 2015 14:53:38 GMT+0000 (UTC)
it stores everything either in $IPFS_PATH or ~/.ipfs if the environment variable is not set
From @Mithgol on Tue Sep 15 2015 16:46:04 GMT+0000 (UTC)
A portable application would use $IPFS_PATH, then ./.ipfs (if exists as a subdirectory in the application’s directory), then ~/.ipfs.
What is the correct repository to open a feature request about it?
From @jbenet on Tue Sep 15 2015 17:56:39 GMT+0000 (UTC)
> then ./.ipfs (if exists as a subdirectory in the application’s directory)
There are uses for this, and i’d also like to follow git semantics, but I’m not yet convinced it’s TRTTD. there’s an issue about this in this tracker, i think. if not, open one, sure
From @whyrusleeping on Tue Sep 15 2015 19:13:58 GMT+0000 (UTC)
@Mithgol the go-ipfs repo would be the correct repo to file an issue in.
From @Mithgol on Tue Sep 15 2015 20:08:54 GMT+0000 (UTC)
Thanks, an issue is created (ipfs/go-ipfs#1707).
This FAQ entry may now be closed.
From @jbenet on Tue Sep 15 2015 20:38:07 GMT+0000 (UTC)
Should we close or leave issues open in this repo? (i’m still wondering tradeoffs of what to do). will people search properly?
From @Mithgol on Wed Sep 16 2015 11:15:22 GMT+0000 (UTC)
They will if they decide to erase is:open from the search bar.
From @Mithgol on Mon Sep 21 2015 06:47:15 GMT+0000 (UTC)
However, as the README says,
All these questions and answers will be compiled into a webpage rendered at IPFS Documentation | IPFS Docs
so maybe the issues should be kept open until that compilation.
On the other hand, maybe it’s quite the contrary because only the answered (and closed) FAQs should be treated as the ones ready for compilation.
From @jbenet on Thu Oct 29 2015 22:06:50 GMT+0000 (UTC)
I’ll reopen to make this easier to find
Any chances to create version for portableapps ?? Or something similar ?