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

node js ipfs on windows #861

Closed
nezzard opened this Issue May 22, 2017 · 30 comments

Comments

Projects
None yet
6 participants
@nezzard

nezzard commented May 22, 2017

Hi, i'm tried to install ipfs from npm on windows 10, but i always get an errors. So i have question, can i install ipfs on windows, or it's only for linux?

@VictorBjelkholm

This comment has been minimized.

Show comment
Hide comment
@VictorBjelkholm

VictorBjelkholm May 22, 2017

Member

Don't think there is something that should stop it from working, but not sure how well tested js-ipfs is on windows. It'll help a lot of you post a full log of the errors and also the output from npm version

Member

VictorBjelkholm commented May 22, 2017

Don't think there is something that should stop it from working, but not sure how well tested js-ipfs is on windows. It'll help a lot of you post a full log of the errors and also the output from npm version

@nezzard

This comment has been minimized.

Show comment
Hide comment
@nezzard

nezzard May 22, 2017

npm: '3.10.10', ares: '1.10.1-DEV', http_parser: '2.7.0', icu: '58.2', modules: '48', node: '6.10.3', openssl: '1.0.2k', uv: '1.9.1', v8: '5.1.281.101', zlib: '1.2.11' }

And npm install log
https://pastebin.com/r87NqUHe

And
jsipfs --help C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\interface-datastore\src\key.js:42 throw new Error(Invalid key: ${this.toString()}`)
^

Error: Invalid key: \SHARDING
at new Key (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\interface-datastore\src\key.js:42:13)
at Object. (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\datastore-core\src\sharding.js:12:18)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\datastore-core\src\index.js:5:27)`

nezzard commented May 22, 2017

npm: '3.10.10', ares: '1.10.1-DEV', http_parser: '2.7.0', icu: '58.2', modules: '48', node: '6.10.3', openssl: '1.0.2k', uv: '1.9.1', v8: '5.1.281.101', zlib: '1.2.11' }

And npm install log
https://pastebin.com/r87NqUHe

And
jsipfs --help C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\interface-datastore\src\key.js:42 throw new Error(Invalid key: ${this.toString()}`)
^

Error: Invalid key: \SHARDING
at new Key (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\interface-datastore\src\key.js:42:13)
at Object. (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\datastore-core\src\sharding.js:12:18)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\datastore-core\src\index.js:5:27)`

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid May 23, 2017

Member

Hi @nezzard, thanks for reporting. This is a known issue with some proposed PR changes:

Wanna help us fix this issue? I need to get a Windows VM set up and won't have fast enough connectivity this week to download the full image.

Member

diasdavid commented May 23, 2017

Hi @nezzard, thanks for reporting. This is a known issue with some proposed PR changes:

Wanna help us fix this issue? I need to get a Windows VM set up and won't have fast enough connectivity this week to download the full image.

@diasdavid diasdavid added the bug label May 23, 2017

@nezzard

This comment has been minimized.

Show comment
Hide comment
@nezzard

nezzard May 23, 2017

I tried to make fix from ipfs/interface-datastore#5 but nothing work, i have the same error like before

nezzard commented May 23, 2017

I tried to make fix from ipfs/interface-datastore#5 but nothing work, i have the same error like before

@mkg20001

This comment has been minimized.

Show comment
Hide comment
@mkg20001

mkg20001 May 26, 2017

Contributor

Wanna help us fix this issue? I need to get a Windows VM set up and won't have fast enough connectivity this week to download the full image.

Or you can try https://www.appveyor.com/

Contributor

mkg20001 commented May 26, 2017

Wanna help us fix this issue? I need to get a Windows VM set up and won't have fast enough connectivity this week to download the full image.

Or you can try https://www.appveyor.com/

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Jun 3, 2017

Member

There has been a fixed pushed, merged and released for interface-datastore. Could you confirm if this works now for you?

Member

diasdavid commented Jun 3, 2017

There has been a fixed pushed, merged and released for interface-datastore. Could you confirm if this works now for you?

@nezzard

This comment has been minimized.

Show comment
Hide comment
@nezzard

nezzard Jun 3, 2017

Just npm install ipfs?
If yes, it's not working

nezzard commented Jun 3, 2017

Just npm install ipfs?
If yes, it's not working

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Jun 3, 2017

Member

Oh, that is because I never released the new interface-datastore, shame on me. Try again now :)

Member

diasdavid commented Jun 3, 2017

Oh, that is because I never released the new interface-datastore, shame on me. Try again now :)

@nezzard

This comment has been minimized.

Show comment
Hide comment
@nezzard

nezzard Jun 3, 2017

Did npm uninstall ipfs than install and now get the same error Invalid key: \SHARDING

nezzard commented Jun 3, 2017

Did npm uninstall ipfs than install and now get the same error Invalid key: \SHARDING

@diasdavid diasdavid changed the title from node js ipfs on windows to Running `js-ipfs` on Windows with Node.js Jun 3, 2017

@download13

This comment has been minimized.

Show comment
Hide comment
@download13

download13 Jun 4, 2017

Hey, I'd really like to help get js-ipfs running on windows.

To that end I made a pull request to update the dependency of a dependency of this project: ipld/js-ipld#83

Once that's merged and published the dependency version on here can be updated and we can start looking at whatever the next windows-related bug will be.

download13 commented Jun 4, 2017

Hey, I'd really like to help get js-ipfs running on windows.

To that end I made a pull request to update the dependency of a dependency of this project: ipld/js-ipld#83

Once that's merged and published the dependency version on here can be updated and we can start looking at whatever the next windows-related bug will be.

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Jun 5, 2017

Member

@download13 which version of npm are you using? You shouldn't have this issue since interface-datastore was published as a patch version and ipld-resolver is using semver for that dep.

Could you try doing a fresh npm install on this repo?

Member

diasdavid commented Jun 5, 2017

@download13 which version of npm are you using? You shouldn't have this issue since interface-datastore was published as a patch version and ipld-resolver is using semver for that dep.

Could you try doing a fresh npm install on this repo?

@download13

This comment has been minimized.

Show comment
Hide comment
@download13

download13 Jun 5, 2017

I tried it just now. Still getting

Error: Invalid key: \SHARDING
    at new Key (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\node_modules\interface-datastore\src\key.js:42:13)
    at Object.<anonymous> (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\src\sharding.js:12:18)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\src\index.js:5:27)

download13 commented Jun 5, 2017

I tried it just now. Still getting

Error: Invalid key: \SHARDING
    at new Key (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\node_modules\interface-datastore\src\key.js:42:13)
    at Object.<anonymous> (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\src\sharding.js:12:18)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\src\index.js:5:27)
@download13

This comment has been minimized.

Show comment
Hide comment
@download13

download13 Jun 8, 2017

Isn't this using a package-lock.json file? I thought you had to update them somehow as the dependencies specified there will always be installed.

download13 commented Jun 8, 2017

Isn't this using a package-lock.json file? I thought you had to update them somehow as the dependencies specified there will always be installed.

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Jun 9, 2017

Member

Which version of npm are you using?

Member

diasdavid commented Jun 9, 2017

Which version of npm are you using?

@download13

This comment has been minimized.

Show comment
Hide comment
@download13

download13 Jun 9, 2017

5.0.3

I tried directly replacing interface-datastore@0.2.1 with 0.2.2 in the package-lock.json file.

It turns out datastore-fs and datastore-core both depend on an old version of interface-datastore (0.1.1) so I swapped those out for the new entry as well.

Now the interface-datastore package seems to work fine, but it's giving the following error when I try to build:

Error: Cannot find module 'catbox-memory'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\download\code\open_source\js-ipfs\node_modules\hapi\lib\server.js:6:22)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)

Which doesn't make a lot of sense as I checked that catbox-memory does exist in both the package-lock.json file and in the ./node_modules/hapi/node_modules directory,

download13 commented Jun 9, 2017

5.0.3

I tried directly replacing interface-datastore@0.2.1 with 0.2.2 in the package-lock.json file.

It turns out datastore-fs and datastore-core both depend on an old version of interface-datastore (0.1.1) so I swapped those out for the new entry as well.

Now the interface-datastore package seems to work fine, but it's giving the following error when I try to build:

Error: Cannot find module 'catbox-memory'
    at Function.Module._resolveFilename (module.js:470:15)
    at Function.Module._load (module.js:418:25)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\download\code\open_source\js-ipfs\node_modules\hapi\lib\server.js:6:22)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)

Which doesn't make a lot of sense as I checked that catbox-memory does exist in both the package-lock.json file and in the ./node_modules/hapi/node_modules directory,

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Jun 10, 2017

Member

@download13 that is npm 5 doing its thing, you can delete the local cache or just simply delete the package-lock.json for now.

Member

diasdavid commented Jun 10, 2017

@download13 that is npm 5 doing its thing, you can delete the local cache or just simply delete the package-lock.json for now.

@nezzard

This comment has been minimized.

Show comment
Hide comment
@nezzard

nezzard Jun 12, 2017

I still get the same error

nezzard commented Jun 12, 2017

I still get the same error

@diasdavid diasdavid added the backlog label Jul 3, 2017

@yaananth

This comment has been minimized.

Show comment
Hide comment
@yaananth

yaananth Jul 25, 2017

+1
npm version 5.3.0

> const IPFS = require('ipfs')
Error: Invalid key: \SHARDING
    at new Key (E:\test\node_modules\datastore-core\node_modules\interface-datastore\src\key.js:42:13)
    at Object.<anonymous> (E:\test\node_modules\datastore-core\src\sharding.js:12:18)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (E:\test\node_modules\datastore-core\src\index.js:5:27)

from package-lock.json

"ipfs": {
      "version": "https://registry.npmjs.org/ipfs/-/ipfs-0.25.0.tgz",
      "integrity": "sha1-k1/S3eJjyqXt46rTA2SqmU+mXUI=",
      "requires": {
         ...
        "ipfs-repo": "https://registry.npmjs.org/ipfs-repo/-/ipfs-repo-0.15.0.tgz",

But,
https://github.com/ipfs/js-ipfs/blob/master/package.json
has "ipfs-repo": "~0.17.0", for "0.25.0"
(not sure why?)
I think 0.17.0 should fix it, since https://github.com/ipfs/js-ipfs-repo/blob/0cb46d8896d80977fdcecc3217ece33b1b9ec953/package.json users datastore-fs that uses https://github.com/ipfs/js-datastore-fs/blob/master/package.json 0.3.0 version of interface-datastore

yaananth commented Jul 25, 2017

+1
npm version 5.3.0

> const IPFS = require('ipfs')
Error: Invalid key: \SHARDING
    at new Key (E:\test\node_modules\datastore-core\node_modules\interface-datastore\src\key.js:42:13)
    at Object.<anonymous> (E:\test\node_modules\datastore-core\src\sharding.js:12:18)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (E:\test\node_modules\datastore-core\src\index.js:5:27)

from package-lock.json

"ipfs": {
      "version": "https://registry.npmjs.org/ipfs/-/ipfs-0.25.0.tgz",
      "integrity": "sha1-k1/S3eJjyqXt46rTA2SqmU+mXUI=",
      "requires": {
         ...
        "ipfs-repo": "https://registry.npmjs.org/ipfs-repo/-/ipfs-repo-0.15.0.tgz",

But,
https://github.com/ipfs/js-ipfs/blob/master/package.json
has "ipfs-repo": "~0.17.0", for "0.25.0"
(not sure why?)
I think 0.17.0 should fix it, since https://github.com/ipfs/js-ipfs-repo/blob/0cb46d8896d80977fdcecc3217ece33b1b9ec953/package.json users datastore-fs that uses https://github.com/ipfs/js-datastore-fs/blob/master/package.json 0.3.0 version of interface-datastore

@yaananth

This comment has been minimized.

Show comment
Hide comment
@yaananth

yaananth Jul 25, 2017

bump inipfs-repo happened just two days ago
bc8ffee

yaananth commented Jul 25, 2017

bump inipfs-repo happened just two days ago
bc8ffee

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Jul 25, 2017

Member

@yaananth could you try running directly from the repo?

> git clone https://github.com/ipfs/js-ipfs
> cd js-ipfs
> npm install
# then try one of the examples
Member

diasdavid commented Jul 25, 2017

@yaananth could you try running directly from the repo?

> git clone https://github.com/ipfs/js-ipfs
> cd js-ipfs
> npm install
# then try one of the examples
@yaananth

This comment has been minimized.

Show comment
Hide comment
@yaananth

yaananth Jul 25, 2017

I guess so, atleast I didn't get that SHARDINGerror

 MINGW64 /d/Github Repositories/js-ipfs/examples/basics (master)
$ node index.js
D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:90
                    throw err0;
                    ^

Error: EEXIST: file already exists, mkdir 'C:\Users\testUser\AppData\Local\Temp'
    at Object.fs.mkdirSync (fs.js:891:18)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:71:13)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:77:24)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)

yaananth commented Jul 25, 2017

I guess so, atleast I didn't get that SHARDINGerror

 MINGW64 /d/Github Repositories/js-ipfs/examples/basics (master)
$ node index.js
D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:90
                    throw err0;
                    ^

Error: EEXIST: file already exists, mkdir 'C:\Users\testUser\AppData\Local\Temp'
    at Object.fs.mkdirSync (fs.js:891:18)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:71:13)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:77:24)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
    at sync (D:\Github Repositories\js-ipfs\node_modules\mkdirp\index.js:78:17)
@nezzard

This comment has been minimized.

Show comment
Hide comment
@nezzard

nezzard Aug 13, 2017

throw new Error(Invalid key: ${this.toString()}`)
^

Error: Invalid key: /CIQFX22I3H5YK5MYQ4PI63M2UKZVJOP5K63QSXHXEIWE4GSQ6LC4UMQ
at new Key (C:\ipfs\node_modules\interface-datastore\src\key.js:45:13)
at keyFromBuffer (C:\ipfs\node_modules\ipfs-repo\src\blockstore.js:20:10)
at cidToDsKey (C:\ipfs\node_modules\ipfs-repo\src\blockstore.js:30:10)
at Object.has (C:\ipfs\node_modules\ipfs-repo\src\blockstore.js:129:17)
at waterfall (C:\ipfs\node_modules\ipfs-bitswap\src\index.js:237:31)
at nextTask (C:\ipfs\node_modules\async\waterfall.js:16:14)
at exports.default (C:\ipfs\node_modules\async\waterfall.js:26:5)
at Bitswap.put (C:\ipfs\node_modules\ipfs-bitswap\src\index.js:236:5)
at BlockService.put (C:\ipfs\node_modules\ipfs-block-service\src\index.js:61:28)
at waterfall (C:\ipfs\node_modules\ipld-resolver\src\index.js:351:28)`

nezzard commented Aug 13, 2017

throw new Error(Invalid key: ${this.toString()}`)
^

Error: Invalid key: /CIQFX22I3H5YK5MYQ4PI63M2UKZVJOP5K63QSXHXEIWE4GSQ6LC4UMQ
at new Key (C:\ipfs\node_modules\interface-datastore\src\key.js:45:13)
at keyFromBuffer (C:\ipfs\node_modules\ipfs-repo\src\blockstore.js:20:10)
at cidToDsKey (C:\ipfs\node_modules\ipfs-repo\src\blockstore.js:30:10)
at Object.has (C:\ipfs\node_modules\ipfs-repo\src\blockstore.js:129:17)
at waterfall (C:\ipfs\node_modules\ipfs-bitswap\src\index.js:237:31)
at nextTask (C:\ipfs\node_modules\async\waterfall.js:16:14)
at exports.default (C:\ipfs\node_modules\async\waterfall.js:26:5)
at Bitswap.put (C:\ipfs\node_modules\ipfs-bitswap\src\index.js:236:5)
at BlockService.put (C:\ipfs\node_modules\ipfs-block-service\src\index.js:61:28)
at waterfall (C:\ipfs\node_modules\ipld-resolver\src\index.js:351:28)`

@diasdavid diasdavid changed the title from Running `js-ipfs` on Windows with Node.js to Windows support Sep 1, 2017

@diasdavid diasdavid changed the title from Windows support to node js ipfs on windows Sep 13, 2017

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid
Member

diasdavid commented Sep 13, 2017

@download13

This comment has been minimized.

Show comment
Hide comment
@download13

download13 Sep 13, 2017

Just to make sure, these keys are only over used on one computer, correct?

I mean, a key isn't constructed on one machine, then sent to another machine.

download13 commented Sep 13, 2017

Just to make sure, these keys are only over used on one computer, correct?

I mean, a key isn't constructed on one machine, then sent to another machine.

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 13, 2017

Member

@download13 correct. Key is used as the path and it is only known to the repo.

Member

diasdavid commented Sep 13, 2017

@download13 correct. Key is used as the path and it is only known to the repo.

@download13

This comment has been minimized.

Show comment
Hide comment
@download13

download13 Sep 13, 2017

@diasdavid So repos are not intended to be moved between machines? In that case is there a way to import/export all the important data in a repository? I know about the ipfs key commands, but can you easily bring over pinned hashes/ipns bindings/etc?

Sorry that's a little off topic, it just seems like something to consider if you can't assume a repo created on one machine will work on another.

download13 commented Sep 13, 2017

@diasdavid So repos are not intended to be moved between machines? In that case is there a way to import/export all the important data in a repository? I know about the ipfs key commands, but can you easily bring over pinned hashes/ipns bindings/etc?

Sorry that's a little off topic, it just seems like something to consider if you can't assume a repo created on one machine will work on another.

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 14, 2017

Member

@download13 a repo from a machine should be usable on another machine.

ipfs key is not related to Repo keys. an IPFS Repo uses internally multiple instances of storage drivers that use interface-datastore which is an interface for a key value store, the key in IPFS Repo comes from Key Value Store

Member

diasdavid commented Sep 14, 2017

@download13 a repo from a machine should be usable on another machine.

ipfs key is not related to Repo keys. an IPFS Repo uses internally multiple instances of storage drivers that use interface-datastore which is an interface for a key value store, the key in IPFS Repo comes from Key Value Store

@download13

This comment has been minimized.

Show comment
Hide comment
@download13

download13 Sep 14, 2017

@diasdavid So if I wanted to move a repo from a windows computer over to a linux vps, I'd be outta luck?

download13 commented Sep 14, 2017

@diasdavid So if I wanted to move a repo from a windows computer over to a linux vps, I'd be outta luck?

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 14, 2017

Member

@download13 you work out of the box. A repo is just a bunch of files and paths

Member

diasdavid commented Sep 14, 2017

@download13 you work out of the box. A repo is just a bunch of files and paths

@diasdavid diasdavid added ready P2 - Medium and removed backlog labels Oct 13, 2017

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Nov 10, 2017

Member

Windows support is here! Celebrate with us at #1017 (comment)

Member

diasdavid commented Nov 10, 2017

Windows support is here! Celebrate with us at #1017 (comment)

@diasdavid diasdavid closed this Nov 10, 2017

@wafflebot wafflebot bot removed the ready label Nov 10, 2017

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