Suggestion: Implement this updated config file

[master3395]

I propose the implementation of a JSON-based configuration file for webhook-proxy.
This structure provides several key benefits, including maintainability, scalability, and enhanced usability. Below, I outline the reasons for its adoption using the provided example configuration:

1. Centralized and Flexible Configuration
   A single JSON configuration file makes it easier to manage all application settings in one place.
   Modular settings (e.g., queue, redis, logging) allow users to customize specific areas of the application without altering the codebase.
   JSON is widely supported and easily editable, making it accessible for developers and system administrators.

2. Enhanced Scalability
   The provided configuration introduces scalable features:

Queue Management:

RabbitMQ support is enhanced with retry policies (maxRetries, delay) and a dead-letter exchange (x-dead-letter-exchange) for unprocessable messages, ensuring reliable and fault-tolerant queue handling.
TTL (Time-To-Live) ensures message expiration, preventing queue overloading.
Redis Configuration:
Includes maxMemory and evictionPolicy to optimize resource usage for high-throughput environments.
Allows users to fine-tune Redis behavior, ensuring optimal performance under heavy loads.

3. Improved Error and Abuse Handling
   The configuration includes options for automatic abuse detection and handling:
   abuseThreshold and abuseHandling (e.g., blockDuration, logAbuse) mitigate malicious or excessive requests, improving system stability.
   Logging critical abuse information ensures better debugging and monitoring.
   Error handling is enhanced with separate info and errorFile logs, providing clearer diagnostics and improving maintainability.

4. Simplified Deployment and Automation
   By externalizing configuration, users can:
   Version-control settings (e.g., in .env.json).
   Use the same codebase across multiple environments (development, staging, production) by swapping configuration files.
   Avoid hardcoding settings, improving security and deployment flexibility.

5. Readability and Maintainability
   The JSON structure is straightforward, making it easier for new developers or maintainers to understand the system's setup.
   The hierarchy in the example (queue, redis, logging) mirrors application architecture, providing intuitive organization.
   Proposed Example Configuration
   The following example demonstrates how a JSON-based configuration file can provide a robust and scalable solution:

File location on current config file:
https://github.com/lewisakura/webhook-proxy/blob/master/config.example.json

{
  "port": 8080,
  "trustProxy": true,
  "autoBlock": true,
  "queue": {
    "enabled": true,
    "rabbitmq": "amqp://localhost",
    "queue": "webhook-proxy",
    "durable": true,
    "retry": {
      "enabled": true,
      "maxRetries": 3,
      "delay": 10000
    },
    "ttl": 60000,
    "x-dead-letter-exchange": "webhook-proxy-dead"
  },
  "redis": "redis://127.0.0.1/0",
  "redisOptions": {
    "maxMemory": "1gb",
    "maxClients": 1000,
    "evictionPolicy": "allkeys-lru"
  },
  "abuseThreshold": 20,
  "abuseHandling": {
    "blockDuration": 3600000,
    "logAbuse": true
  },
  "messageTimeout": 120000,
  "logging": {
    "level": "info",
    "file": "/root/.pm2/logs/webhook-proxy.log",
    "errorFile": "/root/.pm2/logs/webhook-proxy-error.log"
  }
}

Conclusion
Adopting a JSON-based configuration file like the one above will streamline the user experience, enhance system flexibility, and future-proof the application for evolving requirements. It aligns with modern best practices and improves the maintainability of the webhook-proxy project.

Let me know if you'd like help implementing this feature or further refining the suggestion!