See Demo
General
Admin Panel

App Config

Manage application-wide configuration settings from the admin panel.

The App Config section of the admin panel allows you to view and manage application-wide configuration settings that control various aspects of your application's behavior.

Features

View Configuration

The app config table displays all configuration settings:

  • Setting Key - Configuration setting identifier
  • Value - Current configuration value
  • Type - Data type (string, number, boolean, object)
  • Description - What the setting controls
  • Last Updated - When the setting was last modified

Update Configuration

Modify application settings directly from the admin panel:

  • Edit Values - Update configuration values
  • Validation - Settings are validated before saving
  • History - Track changes to configuration over time

Configuration Settings

Common configuration settings include:

Application Settings

  • App Name - Application display name
  • Base URL - Application base URL
  • Contact Information - Support email, phone, address
  • Feature Flags - Enable/disable features

Feature Configuration

  • Marketing Site - Enable/disable marketing pages
  • SaaS Features - Enable/disable SaaS functionality
  • Organizations - Organization-related settings
  • Pagination - Default pagination limits

Theme Settings

  • Default Theme - Default theme (light, dark, system)
  • Available Themes - List of available themes

Configuration Management

Application configuration is managed through configuration files in the config/ directory, not through the admin panel. These files include:

  • config/app.config.ts - Application-wide settings (app name, base URL, feature flags, pagination limits)
  • config/auth.config.ts - Authentication settings
  • config/billing.config.ts - Billing and subscription configuration
  • config/storage.config.ts - File storage configuration

To modify application configuration, edit these files directly in your codebase and redeploy.

Configuration Management

Best Practices

Configuration Changes

  • Document all configuration changes - Test changes in development first - Review changes before applying - Maintain configuration backups

Configuration Security

  • Restrict access to sensitive settings - Validate all configuration values
  • Audit configuration changes - Use environment variables for secrets

Configuration Versioning

  • Track configuration history - Maintain change logs - Support rollback capabilities - Document configuration dependencies

Configuration Sources

Configuration can come from multiple sources:

  1. Database - Stored in the database (managed via admin panel)
  2. Environment Variables - Set via .env files
  3. Config Files - Defined in config/ directory
  4. Runtime - Computed at runtime

The admin panel manages database-stored configuration, while other sources are managed through code and environment variables.

Related Documentation