Configuration

Binacle.Net is designed for flexibility, allowing you to enable only the features you need. Most functionality is provided through modules, each with its own requirements, configuration options, and dependencies.

This guide covers the configuration system for v3.0.x version.

Make sure to read Configuration Basics first then proceed with the specifics for this version.


πŸ“– Table of Contents


πŸ“‚ Configuration Files

All configuration files are located in /app/Config_Files.

πŸ“‘ Directory Structure

app
└── Config_Files
    β”œβ”€β”€ Presets.json
    β”œβ”€β”€ Cors.json
    β”œβ”€β”€ ForwardedHeaders.json
    └── DiagnosticsModule
        β”œβ”€β”€ HealthChecks.json
        β”œβ”€β”€ OpenTelemetry.json
        β”œβ”€β”€ PackingLogs.json
        └── Serilog.json

ForwardedHeaders.json ships with the feature turned off. Cors.json is not in the image at all - add it only if a browser calls the API directly, since until you do, no origin is allowed through.


πŸ”§ Binacle.Net Modules Overview

Each module adds functionality to Binacle.Net. This section provides an overview and links to detailed configuration pages.

πŸ—οΈ Binacle.Net Core

The foundation of Binacle.Net. Provides essential API functionality, Swagger UI, and presets.

πŸ“Š Diagnostics Module

Handles system health monitoring, logging, and telemetry. This module is always enabled, but not all of its features come enabled by default.

πŸ›‘οΈ Service Module

Allows Binacle.Net to run as a managed service with authentication and rate limiting.

This module is primarily made for the official Binacle.Net cloud service. It is still possible to enable it for self-hosted instances, but no public documentation is provided for it. A minor release can break it; a patch will not.

Please refer to the Service Module page for more details.

πŸ–₯️ UI Module

Adds two browser pages: a packing demo and a ViPaq decoder.