######################################################################################
#
#                             Server Manager Configuration
#                               (c) 2026 Emperor Servers
#                                  emperorservers.com
#
#      Please note, the server manager must be restarted for changes made in this
#      configuration file to apply!
#
#      Support:
#          Wiki:    https://wiki.emperorservers.com/
#          Email:   support@emperorservers.com
#          Discord: https://discord.gg/MgJAqFX
#          Forum:   https://forum.emperorservers.com
#
######################################################################################

######################################################################################
# http - configure the web interface on which you access server manager
######################################################################################
http:
  # hostname - the address that server manager listens on. If you don't know what this
  # is, you can leave it as the default! Please note that values containing '0.0.0.0'
  # will be accessible (firewall permitting) outside the local machine you are
  # running server manager on. Change to 127.0.0.1 if you don't want this!
  hostname: 0.0.0.0:8774

  # session_key - a secret value that is used to encrypt session data.
  # PLEASE CHANGE THIS TO A RANDOMLY GENERATED SECURE VALUE.
  session_key:  thisisasessionkey

  # base_url - the public facing base URL for the server manager. Used when server
  # manager generates links to itself. If you're running server manager behind a
  # reverse proxy, you must change this to reflect the correct URL of the server.
  base_url: http://127.0.0.1:8774

  # session_max_age - uncomment this to change the session max age from the default (30 days).
  # session_max_age: 720h

  # session_name_prefix - uncomment this to set a unique prefix for a session. This can be useful if
  # you are running multiple Server Managers on the same hostname (e.g. multiple managers on localhost).
  # Must be alphanumeric, can contain underscores.
  # session_name_prefix: server_manager_1

  tls:
    # TLS configuration. Server Manager supports TLS v1.2 upwards. As of 12/03/2020,
    # the Server Manager configuration yields a perfect score from SSL Labs.
    # Generally we recommend using a Reverse Proxy (caddy, nginx, apache2, etc) instead
    # of this setting.
    # If you enable this, you likely want the hostname (above) to listen on port 443.
    enabled: false
    # the path to the SSL certificate file.
    cert_path: ""
    # the path to the SSL key file.
    key_path: ""

  # this option allows you to disable Cross Site Request Forgery (CSRF) protection.
  # changing this setting is not recommended for most users. If you are scripting HTTP requests to Server Manager,
  # you may wish to enable this setting.
  disable_csrf_protection: false

######################################################################################
# game - configure the setup of the game server itself
######################################################################################
game:
  # install_path - this is the location that the game server is installed. By default,
  # this is 'server', i.e. a folder called 'server' next to your server manager exe
  # file. Change this to anything you like, but be prepared for the manager to
  # complain if it cannot find the game server there!
  install_path: /home/steam/acevo-server

  # executable_name - this is the name of the game server executable file. If left
  # blank then the default executable name will be used (so in most cases, you can leave
  # it blank). If you are running multiple servers on the same Windows machine you
  # may need to rename the server executable for server #2 etc. and then update
  # the executable_name to match here (for example server2.exe).
  # Please note that this does NOT apply to Server Manager's own multiserver setup.
  #
  # It is generally recommended to leave this setting blank.
  executable_name:

######################################################################################
# store: configure the server manager database
######################################################################################
store:
  # path - the location of the server manager JSON store. Usually the default value
  # is fine here.
  path: store.json

######################################################################################
# accounts: configure server manager accounts
######################################################################################
accounts:
  # admin_password_override - if set to a non-empty string, this will become the
  # override password for the 'admin' account. Use this if you have forgotten your
  # admin password. Do not run server manager permanently with this value set!
  admin_password_override: ""

######################################################################################
# recaptcha: configure recaptcha in server manager
######################################################################################
recaptcha:
  site_key: ""
  secret_key: ""

######################################################################################
# server: settings for server manager
######################################################################################
server:
  # disable_windows_browser_open - if set to true on Windows, this will prevent
  # server manager from opening a browser window every time it runs.
  disable_windows_browser_open: false

################################################################################
#
#  monitoring - enabling monitoring allows us to find out more information
#  about how you're using Server Manager, as well as seeing any issues that may
#  occur, so we can collect and fix them. We understand that you may not wish
#  for us to do any monitoring, so you can disable it by setting 'disabled'
#  to true
#
################################################################################
#  with monitoring enabled, the following systems are in place:
#
#  1. Sentry (https://sentry.io) monitoring of both Server Manager's backend
#     code and frontend javascript. This lets us see application errors when
#     they occur.
#
#  2. Google Analytics (https://analytics.google.com) tracking, so we can see how
#     many people use Server Manager, when they use it and where they are in
#     the world.
#
# once again, if you do not wish for Server Manager to do these things, simply
# set 'disabled' to true and monitoring will not take place.
################################################################################
monitoring:
  disabled: false