Closed let4be closed 2 years ago
Partitially solved by lazy.sh
and so called profiles
https://github.com/let4be/crusty/tree/master/infra/profiles/c5.metal
But this needs further improvements
Better solution would be to configure everything in the same config file(to avoid duplication) and simply provide alternative values for several key parameters(scaling points, such as resolver concurrency and domain concurrency) and simply load approapriate values on config parse stage(by a switch via cmd option/env var)
might come in handy: https://github.com/mehcode/config-rs
This could better explain what the primary scaling points are, config for aws's
c5.metal
would be quite different fromt2.micro