adapter: Swoosh.Adapters.SMTP, 
relay: "email-smtp.eu-north-1.amazonaws.com", 
# usually 25 (clear), 465 (TLS) or 587 (STARTTLS) 
port: 587, 
username: "USERNAME", 
password: "PASSWORD", 
# can be `:always` or `:never` 
tls: :if_available, 
# not needed when using STARTTLS 
ssl: false, 
allowed_tls_versions: [:"tlsv1.2", :"tlsv1.3"], 
tls_options: [ 
  verify: :verify_peer, 
  versions: [:"tlsv1.2", :"tlsv1.3"], 
  cacerts: :public_key.cacerts_get(), 
  server_name_indication: "localhost", 
  depth: 99 
], 
retries: 2, 
# can be `true` 
no_mx_lookups: false, 
# can be `:always`. If your smtp relay requires authentication set it to `:always`. 
auth: :if_available

In reply to @mydemoaccount:matrix.org
What is the reason Mobilizon uses postgis? I have never heard of that before, but that may be my fault. Now it is stopping me from running mobilizon on a raspberry pi since there is no docker image for postgis that runs on the arm achitecture :( Any advice on how to do this?

Ok how do I set locales? The reference doesn't tell. I tried this, but no effect:

config :cldr, 
  locales: [ "fi_FI", "en_GB" ]

Ok got forward but:

mobilizon-1  | ERROR! the application :mobilizon has a different value set for key :cldr during runtime compared to compile time. Since this application environment entry was marked as compile time, this difference can lead to different behaviour than expected:
mobilizon-1  | 
mobilizon-1  |   * Compile time value was set to: [locales: ["ar", "be", "bn", "ca", "cs", "cy", "de", "en", "es", "fa", "fi", "fr", "gd", "gl", "hr", "hu", "id", "it", "ja", "nl", "nn", "pl", "pt", "ru", "sv", "zh_Hant"]]
mobilizon-1  |   * Runtime value was set to: [locales: ["fi", "en"]]
mobilizon-1  | 
mobilizon-1  | To fix this error, you might:
mobilizon-1  | 
mobilizon-1  |   * Make the runtime value match the compile time one
mobilizon-1  | 
mobilizon-1  |   * Recompile your project. If the misconfigured application is a dependency, you may need to run "mix deps.clean mobilizon --build"
mobilizon-1  | 
mobilizon-1  |   * Alternatively, you can disable this check. If you are using releases, you can set :validate_compile_env to false in your release configuration. If you are using Mix to start your system, you can pass the --no-validate-compile-env flag