[bisq-network/roles] Markets Website+API Operator/Maintainer (#9)

[wiz]

## Cycle 16/17 report

It took a while, but we've finally migrated the Bisq Markets API away from the old LAMP architecture to its new optimized nginx+NodeJS architecture with a reverse proxy cache in front of 2 new servers running the [completely new implementation](https://github.com/mempool/mempool/pull/107/files) by @softsimon as part of https://github.com/bisq-network/projects/issues/41 - performance on the https://bisq.network/markets website is now fast again, and the ops team budget has been updated for the dual node setup.

The Markets API endpoint hostname has also been migrated from `markets.bisq.network/api` to `bisq.markets/api` so this change should be communicated to users of the API, possibly over Twitter and direct communication to them if we have it. The new `bisq.markets` website will have improved API documentation, but for now it just hosts the previous static HTML file as a placeholder until that project is ready to launch.

We're now beginning the new Angular based webapp frontend development phase of https://github.com/bisq-network/projects/issues/41 for the new `bisq.markets` website project - if anyone has any features they want implemented feel free to comment on the project issue.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/roles/issues/9#issuecomment-697146253
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200922/7d064fba/attachment.html>