Skip to content
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

./run.sh not Windows compatible - can be removed entirely. (Updated package.json attached.) #20

Open
TinosNitso opened this issue Aug 25, 2022 · 0 comments

Comments

@TinosNitso
Copy link

TinosNitso commented Aug 25, 2022

In Windows 10 I've used both slpserve & slpdb by removing lines 6→8 of fountainhead-core's package.json, & updating a whole bunch of dependencies. From memory I had to update at least one (maybe zeromq) so then I just updated lots of the other ones. There are more updates possible but I didn't bother. Here is my full list:

  "dependencies": {
    "async": "^2.6.2",
    "bignumber.js": "~9.0.0",
    "bitcoind-rpc": "^0.7.2",
    "bitcore-lib-cash": "^8.25.36",
    "child_process": "^1.0.2",
    "cors": "^2.8.4",
    "dotenv": "16.0.1",
    "express": "^4.16.4",
    "ip": "^1.1.8",
    "json-pointer": "^0.6.0",
    "mingo": "6.1.0",
    "mongodb": "4.9.0",
    "node-jq": "2.3.3",
    "sinon": "^7.3.2",
    "traverse": "^0.6.6",
    "zeromq": "^5.2.8"
  },
  "devDependencies": {
    "chai": "^4.2.0",
    "chai-spies": "^1.0.0",
    "deep-diff": "^1.0.2",
    "eslint": "^5.16.0",
    "mocha": "7.2.0",
    "rewire": "^4.0.1"
  }

I've attached my package.json here.

It turns out nodejs is extremely slow in Win10 in my experience, so I'll prob just switch back to using WSL1 (Windows Subsystem for Linux). It may be to do with having only 1GB/23GB RAM (& the rest on SSD).
I currently have an slpdb instance syncing at slpdb.tinos.ml.
I also have a sync journal on Reddit, here.

@TinosNitso TinosNitso changed the title ./run.sh not Windows compatible - can be removed entirely. (Updated package.json attached.) ./run.sh not Windows compatible - can be removed entirely. (Updated package.json attached.) Aug 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant