# This file is responsible for configuring your application
# and its dependencies with the aid of the Mix.Config module.
use Mix.Config
import_config "#{Mix.env}.exs"

#-------------------------------
#  ENGINE
#-------------------------------

# Choose the event storage, can be Engine.Storage.Eventstore
# or Engine.Storage.Postgres

config :engine,
  storage: Engine.Storage.Eventstore,
  nodes: [:'master@localhost', :'slave1@localhost'],          # to use with SYN if we have many nodes
  snapshot_period: 50

#-------------------------------
#  EXTREME [Eventstore Driver]
#-------------------------------


config :extreme, :event_store,
  db_type: :node,
  host: "localhost",
  port: 1113,
  username: "admin",
  password: "changeit",
  reconnect_delay: 2_000,
  max_attempts: :infinity


#-------------------------------
#  LOGGER
#-------------------------------

# see config/dev.exs , config/test.exs, etc



# This configuration is loaded before any dependency and is restricted
# to this project. If another project depends on this project, this
# file won't be loaded nor affect the parent project. For this reason,
# if you want to provide default values for your application for
# 3rd-party users, it should be done in your "mix.exs" file.

# You can configure for your application as:
#
#     config :engine, key: :value
#
# And access this configuration in your application as:
#
#     Application.get_env(:engine, :key)
#
# Or configure a 3rd-party app:
#
#     config :logger, level: :info
#

# It is also possible to import configuration files, relative to this
# directory. For example, you can emulate configuration per environment
# by uncommenting the line below and defining dev.exs, test.exs and such.
# Configuration from the imported file will override the ones defined
# here (which is why it is important to import them last).
#
#     import_config "#{Mix.env}.exs"