3 # For development, we disable any cache and enable
4 # debugging and code reloading.
6 # The watchers configuration can be used to run external
7 # watchers to your application. For example, we use it
8 # with brunch.io to recompile .js and .css sources.
9 config :pleroma, Pleroma.Web.Endpoint,
19 # In order to use HTTPS in development, a self-signed
20 # certificate can be generated by running the following
21 # command from your terminal:
23 # openssl req -new -newkey rsa:4096 -days 365 -nodes -x509 -subj "/C=US/ST=Denial/L=Springfield/O=Dis/CN=www.example.com" -keyout priv/server.key -out priv/server.pem
25 # The `http:` config above can be replaced with:
27 # https: [port: 4000, keyfile: "priv/server.key", certfile: "priv/server.pem"],
29 # If desired, both `http:` and `https:` keys can be
30 # configured to run both http and https servers on
33 # Do not include metadata nor timestamps in development logs
34 config :logger, :console, format: "[$level] $message\n"
36 # Set a higher stacktrace during development. Avoid configuring such
37 # in production as building large stacktraces may be expensive.
38 config :phoenix, :stacktrace_depth, 20
40 # Configure your database
41 config :pleroma, Pleroma.Repo,
42 adapter: Ecto.Adapters.Postgres,
45 database: "pleroma_dev",
46 hostname: "localhost",