There are complementary PRs in the exrproxy and exrproxy-env repos of the same name which should be merged simultaneously with this one.
Note: The changes in this PR have only been about 75% tested. It really should be tested by others; not just me! That said, the easiest way to make it possible for others to test these changes is to merge this to master so a new docker image for the Payment Processor will be built and uploaded as the latest image on docker hub. This is obviously not good standard practice, but should be fine atm considering there are exactly ZERO people currently using the Payment Processor.
This PR closes the following issues:
https://github.com/blocknetdx/eth-payment-processor/issues/31 https://github.com/blocknetdx/eth-payment-processor/issues/27 https://github.com/blocknetdx/eth-payment-processor/issues/28 https://github.com/blocknetdx/exrproxy-env/issues/206 https://github.com/blocknetdx/exrproxy-env/issues/203 https://github.com/blocknetdx/exrproxy-env/issues/204 https://github.com/blocknetdx/exrproxy-env/issues/178
The behavior the Payment Processor will have after this PR is merged is described in the (freshly updated) Projects section of the API docs: https://api.blocknet.org/#projects-api-xquery-hydra
The SNode deployment docs (https://docs.blocknet.org/service-nodes/setup/#deploy-enterprise-xrouter-environment) have also been updated to reflect the changes made in this PR.
There are complementary PRs in the
exrproxyandexrproxy-envrepos of the same name which should be merged simultaneously with this one.Note: The changes in this PR have only been about 75% tested. It really should be tested by others; not just me! That said, the easiest way to make it possible for others to test these changes is to merge this to
masterso a new docker image for the Payment Processor will be built and uploaded as thelatestimage on docker hub. This is obviously not good standard practice, but should be fine atm considering there are exactly ZERO people currently using the Payment Processor.