Troy McConaghy

@cboothe followed up by writing: > Any tips for the moment? It is setting up a user specific monit.rc right now instead of in the system

Under **Confirmed use cases**, there are some which begin "As BigchainDB I want…" Who is the 'I' in these sentences? Is it the employees of BigchainDB GmbH, the company? Or...

I'm keeping this keeping this open as a source for some potential BigchainDB Enhancement Proposal. There might be some good ideas to pick out. Then we will close it.

Notes: - Many HTTP endpoints can be removed, because we intend to let node operators just connect to their local MongoDB directly to do whatever [MongoDB operations](https://docs.mongodb.com/manual/crud/) they like, with...

To do: - [ ] Write a proper [BEP](https://github.com/bigchaindb/BEPs) to replace this issue. - [ ] Close this issue.

Note: The purpose of the sentry nodes is to prevent a directed denial of service (DoS) attack on the current proposer node. We discussed DoS attack mitigation in the past,...

[BEP-19](https://github.com/bigchaindb/BEPs/tree/master/19) recommends putting a sentry node (which it calls a "sentinel server") in front of each node, with the additional property that it gives the node a break every 100...

I don't understand how you installed everything, configured them, then started them running. I see Monit being used, but then you say you're using Docker? That seems inconsistent.

To run BigchainDB, you must also run MongoDB and Tendermint, so we have some Docker Compose stuff to make that easy. See http://docs.bigchaindb.com/projects/contributing/en/latest/dev-setup-coding-and-contribution-process/run-node-with-docker-compose.html

Related: issue #662