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,
18 # In order to use HTTPS in development, a self-signed
19 # certificate can be generated by running the following
20 # command from your terminal:
22 # 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
24 # The `http:` config above can be replaced with:
26 # https: [port: 4000, keyfile: "priv/server.key", certfile: "priv/server.pem"],
28 # If desired, both `http:` and `https:` keys can be
29 # configured to run both http and https servers on
32 # Do not include metadata nor timestamps in development logs
33 config :logger, :console, format: "[$level] $message\n"
35 # Set a higher stacktrace during development. Avoid configuring such
36 # in production as building large stacktraces may be expensive.
37 config :phoenix, :stacktrace_depth, 20
39 # Configure your database
40 config :pleroma, Pleroma.Repo,
41 adapter: Ecto.Adapters.Postgres,
44 database: "pleroma_dev",
45 hostname: "localhost",