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,
12 protocol_options: [max_request_line_length: 8192, max_header_value_length: 8192]
20 config :pleroma, Pleroma.Mailer, adapter: Swoosh.Adapters.Local
24 # In order to use HTTPS in development, a self-signed
25 # certificate can be generated by running the following
26 # command from your terminal:
28 # 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
30 # The `http:` config above can be replaced with:
32 # https: [port: 4000, keyfile: "priv/server.key", certfile: "priv/server.pem"],
34 # If desired, both `http:` and `https:` keys can be
35 # configured to run both http and https servers on
38 # Do not include metadata nor timestamps in development logs
39 config :logger, :console, format: "[$level] $message\n"
41 # Set a higher stacktrace during development. Avoid configuring such
42 # in production as building large stacktraces may be expensive.
43 config :phoenix, :stacktrace_depth, 20
45 # Configure your database
46 config :pleroma, Pleroma.Repo,
47 adapter: Ecto.Adapters.Postgres,
50 database: "pleroma_dev",
51 hostname: "localhost",
54 if File.exists?("./config/dev.secret.exs") do
55 import_config "dev.secret.exs"
58 "!!! RUNNING IN LOCALHOST DEV MODE! !!!\nFEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs"