You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,17 @@ query {
22
22
}
23
23
```
24
24
25
+
## Running in production
26
+
27
+
The provided docker compose setup is a minimal configuration best suitable for dev and testing envorinmonents. For a stable production deployment we recommend the following.
28
+
29
+
- Use a private gRPC endpoint (`WS_PROVIDER_ENDPOINT_URI` env variable)
30
+
- Use managed Postgres database with non-root access (`DB_*` env variables)
31
+
- Collect and monitor [Prometheus](https://prometheus.io/) metrics exposed at port 9090
32
+
- Increase `WORKERS_NUMBER` to speed up the syncing. Usually somewhere between 5-50 workers is a sweet spot depending on the gRPC endpoint capacity.
33
+
34
+
To reliably run a Squid Archive we recommend 16GB RAM and modern CPU. Database storage requirements depend on the size of the network. A rule of thumb is to reserve around 100 kb per block, so e.g. for Kusama with ~10M blocks one needs about 1Tb for Postgres storage.
35
+
25
36
## Type definitons updates
26
37
27
38
Most chains publish type definitions as an npm package. Some archives (e.g. shiden or bifrost) has a script `gen-types.js` for generating the json type defintions. To update, run from the corresponding folder
0 commit comments