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
Chronicle requires configuration to define its runtime behavior. For complete configuration details, see the [Configuration](configuration.md) guide.
21
+
Chronicle requires configuration to define its runtime behavior. For complete configuration details, see the [Configuration](hosting/configuration.md) guide.
22
22
23
23
The configuration file must be mounted into the container at `/app/chronicle.json`, or you can use environment variables with the `Cratis__Chronicle__` prefix.
24
24
@@ -80,11 +80,11 @@ volumes:
80
80
1. **Use specific version tags** instead of `latest` for production deployments
81
81
2. **Mount configuration as read-only** (`-v /path/to/chronicle.json:/app/chronicle.json:ro`)
82
82
3. **Use environment-specific connection strings** for MongoDB
83
-
4. **Configure appropriate timeouts** based on your infrastructure (see [Configuration](configuration.md))
83
+
4. **Configure appropriate timeouts** based on your infrastructure (see [Configuration](hosting/configuration.md))
84
84
5. **Enable health checks** for container orchestration
85
85
6. **Set up monitoring** for all exposed ports
86
86
7. **Use secrets management** for sensitive configuration values
87
-
8. **Enable TLS** with proper certificates (see [TLS Configuration](../tls-configuration.md))
87
+
8. **Enable TLS** with proper certificates (see [TLS Configuration](../tls-hosting/configuration.md))
0 commit comments