Administration/Configuration Files

Log Configuration

Gigantics allows you to configure the location where log files are stored. By default, logs are stored in a local ./logs/out.txt file, but you can customize this path to meet your system requirements.

Configuration File

Log directory configuration is done through the config/default.yaml file. Add or modify the logs property to change where log files are stored.

Windows Configuration

For Windows systems, specify the full path to your desired log directory:

# config/default.yaml
logs: 'C:\ProgramData\Gigantics\logs\out.txt'

You can also use relative paths or other Windows-specific locations:

# Examples for Windows
logs: '.\logs\out.txt'              # Relative path (default)
logs: 'C:\Logs\Gigantics\out.txt'  # Custom directory
logs: 'D:\AppData\logs\out.txt'    # Different drive

Linux Configuration

For Linux systems, specify the full path to your desired log directory:

# config/default.yaml
logs: '/var/log/gigantics/out.txt'

You can use any valid Linux path:

# Examples for Linux
logs: './logs/out.txt'              # Relative path (default)
logs: '/var/log/gigantics/out.txt'  # System log directory
logs: '/opt/gigantics/logs/out.txt' # Custom directory
logs: '/home/user/gigantics/logs/out.txt' # User directory

Directory Permissions

Ensure that the user running the Gigantics application has write permissions to the specified log directory:

  • Windows: The user running gig.exe should have write access to the specified directory
  • Linux: The user running the application should have write access to the specified directory

Best Practices

  1. Use dedicated log directories: Store logs in a dedicated directory like /var/log/gigantics on Linux or C:\ProgramData\Gigantics\logs on Windows

  2. Ensure sufficient disk space: Log files can grow large over time, so choose a location with adequate storage

  3. Set appropriate permissions: Make sure the log directory is secure and only accessible by authorized users

  4. Use absolute paths: For production environments, use absolute paths to avoid ambiguity

Testing the Configuration

After modifying the configuration file, restart the Gigantics application to apply the changes. The application will automatically create the log file at the specified location if it doesn't exist.

On this page