# Configuration



Most Krenalis settings can be managed at runtime through the Admin Console or the API. However, some settings are only read at startup from environment variables, such as those that configure the Krenalis server, HTTPS certificates, the primary application database, and NATS servers.

<ul class="cards" data-columns="2">
  <li>
    <a href="configuration/with-docker-compose">
      <figure><img src="%3cp%3e/docs/images/compose-file.svg%3c/p%3e%0a" alt="Compose files"></figure>
      <div>With Docker Compose</div>
      <p>Personalize the environment variables when starting Krenalis with our Docker Compose file.</p>
    </a>
  </li>
  <li>
    <a href="configuration/environment-variables">
      <figure><img src="%3cp%3e/docs/images/list.svg%3c/p%3e%0a" alt="Environment variables"></figure>
      <div>Environment variables</div>
      <p>All the environment variables that Krenalis reads at startup.</p>
    </a>
  </li>
  <li>
    <a href="configuration/env-file">
      <figure><img src="%3cp%3e/docs/images/env-file.svg%3c/p%3e%0a" alt=".env file"></figure>
      <div>.env file</div>
      <p>Personalize the environment variables, for source installations, used to start Krenalis.</p>
    </a>
  </li>
  <li>
    <a href="configuration/aws-parameter-store">
      <figure><img src="%3cp%3e/docs/images/aws.svg%3c/p%3e%0a" alt="AWS"></figure>
      <div>AWS Parameter Store</div>
      <p>Load startup settings from AWS Parameter Store and Secrets Manager.</p>
    </a>
  </li>
</ul>