Any chance of some instructions on how to update P2Pools, thanks.
We will double check this! Thanks! I didn't even stop P2pool, I just stopped the DigiByte client, replaced it with the newer version, and relaunched it.
My node kept on running all the time and picked up new work as soon as the client was relaunched.
I didn't touch the P2Pool config yet.
@All P2Pool Owners:
The P2Pool Config also needs to be updated. I have requested Rav3npl (at Github) to check it out. And I'll let you guys know when the networks.py files are updated.
https://github.com/Rav3nPL/p2pool-rav/issues/57
So Heres how P2Pools can update both digibyte and p2pool config files using the terminal:
How to Update digibyte or DigiByteProject:
change directory to digibyte or digibyteproject
Code:
cd ~
killall digibyted
Code:
cd ~/DigiByteProject/
Code:
cd ~/digibyte
Code:
git pull origin master
You should what changes were made (Deletions and additions in the code) -- Make sure that these changes were made!
And now you can run digibyted again, and as stated by the p2pool owners above, you dont have to stop the client...
How to Update P2Pool Config:
Again, this can ONLY be done after Rav3n or someone from the DigiByteTeam (@xploited) gives us the networks.py files.
So, wait until that happens.
Change directory to p2pool
Code:
cd ~/p2pool
Code:
cd ~/p2pool-rav
Code:
git pull origin master
Doon't worry, when you pull to p2pool.. There are no changes made to the web-static folder.. so you frontend will stay the same
I would recommend killing the p2pool and restarting it just to be safe
We dont want any surprise forks!
