tornadocontrib/web3-proxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

add steps for kafka library

Browse Source
This commit is contained in:
Bryan Stitt 2023-03-03 15:25:44 -08:00
parent 36e4183373
commit 5695c1b06e
2 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -12,9 +12,10 @@ Each server has different limits to configure. The `soft_limit` is the number of
## Quick development
1. Run `docker-compose up -d` to start the database and caches. See `docker-compose.yml` for details.
2. Copy `./config/example.toml` to `./config/development.toml` and change settings to match your setup.
3. Run `cargo` commands:
1. `brew install librdkafka` or `sudo apt-get install librdkafka-dev`
2. Run `docker-compose up -d` to start the database and caches. See `docker-compose.yml` for details.
3. Copy `./config/example.toml` to `./config/development.toml` and change settings to match your setup.
4. Run `cargo` commands:
```
$ cargo run --release -- --help

1
TODO.md
View File

@ -381,6 +381,7 @@ These are not yet ordered. There might be duplicates. We might not actually need
- [ ] all anyhow::Results need to be replaced with FrontendErrorResponse.
- [ ] rename FrontendErrorResponse to Web3ProxyError
- [ ] almost all the anyhows should be Web3ProxyError::BadRequest
- as is, these errors are seen as 500 errors and so haproxy keeps retrying them
- change premium concurrency limit to be against ip+rpckey
- then sites like curve.fi don't have to worry about their user count
- it does mean we will have a harder time capacity planning from the number of keys