Migrate production pricenodes to v0.7.0

[cbeams]

Per #2 and #3, the new home of bisq-pricenode source code is here in the bisq-network/pricenode repository.

@bisq-network/pricenode-operators, this issue is about migrating your production pricenodes from 0.6.4 to 0.7.0.

The code has not changed significantly in this move, but the way the pricenode is started up has changed. You can see complete instructions in the README of this repository.

To be conservative, we should probably do this migration one node at a time, while watching the logs pretty closely on each to ensure nothing goes wrong.

I suggest we do it in the following order:

• @ManfredKarrer migrates the first of his nodes, and watches in closely
• @ManfredKarrer migrates his other two nodes
• @mrosseel migrates his node
• @Emzy migrates his node

Sound good to everyone? Please let me know what questions you have, and let's coordinate in the Slack #pricenode channel as necessary. Thanks!

[cbeams]

Note that I have not actually tagged v0.7.0 yet. I'd like to have @ManfredKarrer work from master to try this out, and if everything looks good, then we can tag the release.

Note that I am not building this as an executable jar at the moment, but we can do that if it's important. As per the README, it's essentially designed to be built and run from source right now.

[ManfredKarrer]

I run the new version now.

[cbeams]

I run the new version now.

Great. It's been three days now, and it sounds like there haven't been any issues.

@mrosseel and @Emzy, could you update now as well?

[mrosseel]

Upgrading now, had to adapt my Dockerfile to use gradle. Still using the old loop scripts waiting for resolution of #6
Will PR the docker setup to the pricenode repo soon.

[mrosseel]

There was already a PR, #1 , please review

[ManfredKarrer]

I have not seen any issues with the change. I think it is safe of @mrosseel and @Emzy move over to the new model as well.

[Emzy]

My node running vesion 0.7.0. now.

[cbeams]

Closing as complete, thanks all!

I’ll follow up soon in a separate issue / conversation about upgrade procedures going forward.