Closed metabsd closed 6 years ago
had this question already https://github.com/Storj/storjshare-daemon/issues/320
Just execute the following commands:
storjshare save
storjshare killall
npm install -g storjshare-daemon
storjshare daemon
storjshare load
this should update to the latest Core Version, when NPM finds a newer version online.
@stefanbenten thanks
storjshare save
storjshare killall
export CC=cc && export CXX=c++ && npm install storjshare-daemon -g
storjshare daemon
storjshare load
storjshare --version
daemon: 5.3.0, core: 8.6.0, protocol: 1.2.0
👋 Hey! Thanks for this contribution. Apologies for the delay in responding!
We've decided to rearchitect Storj, so that we can scale better. You can read more about this decision here. This means that we are entirely focused on v3 at the moment, in the storj/storj repository. Our white paper for v3 is coming very, very soon - follow along on the blog and in our Rocketchat.
As this repository is part of the v2 network, we're no longer maintaining this repository. I am going to close this for now. If you have any questions, I encourage you to jump on Rocketchat and ask them there. Thanks!
Package Versions
Replace the values below using the output from
storjshare --version
.Replace the values below using the output from
node --version
.Expected Behavior
I use the latest version. git clone but I don't have the latest version. Suppose to be 8.6.0.
Actual Behavior
I see 8.5.0
Steps to Reproduce
Please include the steps the reproduce the issue, numbered below. Include as much detail as possible.