Before releasing to testnet, we should have a production-ready configuration and a test-specific configuration.
This issue tracks what is required.
2. Technical Details:
The production configuration should provide sane, secure defaults where possible and fail where others, required value have not been provided by the user.
2.1 Acceptance Criteria:
[ ] The production configuration exists and ships by default to user (e.g. through Docker).
[ ] There's a test configuration, used specifically for tests.
Feature - Prepare a production-ready configuration file
1. Description
The current configuration (eg. https://github.com/stacks-network/sbtc/blob/68b18a477bf7e6530aca30f40588d2dd32814b34/signer/src/config/default.toml) optimizes for tests, not for production.
1.1 Context & Purpose
Before releasing to testnet, we should have a production-ready configuration and a test-specific configuration.
This issue tracks what is required.
2. Technical Details:
The production configuration should provide sane, secure defaults where possible and fail where others, required value have not been provided by the user.
2.1 Acceptance Criteria: