Define install location for Go-IPFS, IPFS Desktop, and IPFS Companion.

[genus1]

I installed IPF desktop but it did not give me a way to have the .ipfs database stored on another drive. Stupid to have large changing files on small ssd c drives.

Then tried to update the go-ipfs from 11 and it would not do it. There needs to be a way to remove the go from the drive then reinstall.

Tried to change the path in the .ipfs-desktop folder. Still did not work.

[welcome[bot]]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review. In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additiona round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment. Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[genus1]

I have tried to add the path for .ipfs into both user and system variables. If I run daemon first, then desktop it will locate to the correct drive and directory. As soon as I run companion it starts a new ipfs back under users and ignors the env variables. The installer for go, desktop, and companion need to allow placing the install in a user selected folder and drive so that C drive SSDs are not overwritten. Has ANYONE reached out the the programmers for the installers of ipfs and coordinated this little challenge that MOST installers have fixed YEARS ago.

[genus1]

Same issue happens when running jsipfs daemon. When Starting IPFS desktop, the desktop will not start because it says the ports 5001 are already in use. This means the Desktop is not reading the environment variable for the path to the .ipfs and database.

[Jorropo]

@genus1 I find that weird that your companion is starting an IPFS node. I don't use that feature, I just let the compnion hail my systemd manage deamon.

Else, can't you just use a symlink ? That maybe a very nixian way of thinking and you seem to be on windows, but if something doesn't cooperate and really want data to be in a place I don't like, I just symlink it. (and windows supports symlink (however they might be an optional feature I don't remember)).

[genus1]

This appears to be a long standing issue with ipfs storing under the USER for windows instead of installing in according to the ENV variables. Windows USER is always the C drive and that is NOT a good place to run an application like IPFS on an SSD.