3 # For production, we often load configuration from external
4 # sources, such as your system environment. For this reason,
5 # you won't find the :http configuration below, but set inside
6 # Pleroma.Web.Endpoint.load_from_system_env/1 dynamically.
7 # Any dynamic configuration should be moved to such function.
9 # Don't forget to configure the url host to something meaningful,
10 # Phoenix uses this information when generating URLs.
12 # Finally, we also include the path to a cache manifest
13 # containing the digested version of static files. This
14 # manifest is generated by the mix phoenix.digest task
15 # which you typically run after static files are built.
16 config :pleroma, Pleroma.Web.Endpoint,
20 # Do not print debug messages in production
21 config :logger, level: :info
25 # To get SSL working, you will need to add the `https` key
26 # to the previous section and set your `:url` port to 443:
28 # config :pleroma, Pleroma.Web.Endpoint,
30 # url: [host: "example.com", port: 443],
33 # keyfile: System.get_env("SOME_APP_SSL_KEY_PATH"),
34 # certfile: System.get_env("SOME_APP_SSL_CERT_PATH")]
36 # Where those two env variables return an absolute path to
37 # the key and cert in disk or a relative path inside priv,
38 # for example "priv/ssl/server.key".
40 # We also recommend setting `force_ssl`, ensuring no data is
41 # ever sent via http, always redirecting to https:
43 # config :pleroma, Pleroma.Web.Endpoint,
44 # force_ssl: [hsts: true]
46 # Check `Plug.SSL` for all available options in `force_ssl`.
50 # If you are doing OTP releases, you need to instruct Phoenix
51 # to start the server for all endpoints:
53 # config :phoenix, :serve_endpoints, true
55 # Alternatively, you can configure exactly which server to
58 # config :pleroma, Pleroma.Web.Endpoint, server: true
61 # Finally import the config/prod.secret.exs
62 # which should be versioned separately.
63 import_config "prod.secret.exs"