Skip to content

Application configuration

Stéphane Brunner edited this page Feb 21, 2024 · 4 revisions

The application will use two configuration files

production.ini

This file will configure:

  • The logging.
  • The GitHub applications.
  • The Database connections.

One advantage of this file is that we can use environment variables.

/etc/ghci/configurations.yaml

In this file, we can configure the profiles and some other little things

APPLICATION-CONFIG.md, JSON schema.

Environment variable

  • TEST_USER The user for the test, should not be defined on production!.
  • VISIBLE_ENTRY_POINT The entry point for the application ('/' by default).
  • GHCI_CONFIGURATION The path to the configuration file.
  • GHCI_SESSION_SECRET The secret used in the cookie session.
  • GHCI_SESSION_SALT The salt used in the cookie session.
  • C2C_AUTH_GITHUB_REPOSITORY The repository on witch one we the test for admin user.
  • C2C_AUTH_GITHUB_SECRET The secret for JWD encryption (required, with a length at least of 16).
  • C2C_AUTH_GITHUB_CLIENT_ID The client id for the GitHub application.
  • C2C_AUTH_GITHUB_CLIENT_SECRET The client secret for the GitHub application.
  • C2C_PROMETHEUS_PORT The port for the Prometheus metrics.