╰─➤ asdf current elixir
1.7.3-otp-21
Yep, though now on 1.7.4-otp-21 on that server. ^.^
Entirely stock/standard, everything is unchanged from the standard phx_new setup:
╰─➤ find config -type f
config/prod.secret.exs
config/config.exs
config/test.exs
config/dev.exs
config/prod.exs
Here are the contents of the two files that matter (since I ran in standard dev mode):
config.exs:
# This file is responsible for configuring your application
# and its dependencies with the aid of the Mix.Config module.
#
# This configuration file is loaded before any dependency and
# is restricted to this project.
# General application configuration
use Mix.Config
config :test_fourteen_bug,
ecto_repos: [TestFourteenBug.Repo]
# Configures the endpoint
config :test_fourteen_bug, TestFourteenBugWeb.Endpoint,
url: [host: "localhost"],
secret_key_base: "m37BfboSxMkut6vHe/N8Qhns2qZZ48knfMJeIHjHdUYPFn5yXzIYfweaLBDh++X/",
render_errors: [view: TestFourteenBugWeb.ErrorView, accepts: ~w(html json)],
pubsub: [name: TestFourteenBug.PubSub, adapter: Phoenix.PubSub.PG2]
# Configures Elixir's Logger
config :logger, :console,
format: "$time $metadata[$level] $message\n",
metadata: [:request_id]
# Use Jason for JSON parsing in Phoenix
config :phoenix, :json_library, Jason
# Import environment specific config. This must remain at the bottom
# of this file so it overrides the configuration defined above.
import_config "#{Mix.env()}.exs"
dev.exs:
use Mix.Config
# For development, we disable any cache and enable
# debugging and code reloading.
#
# The watchers configuration can be used to run external
# watchers to your application. For example, we use it
# with webpack to recompile .js and .css sources.
config :test_fourteen_bug, TestFourteenBugWeb.Endpoint,
http: [port: 4000],
debug_errors: true,
code_reloader: true,
check_origin: false,
watchers: [
node: [
"node_modules/webpack/bin/webpack.js",
"--mode",
"development",
"--watch-stdin",
cd: Path.expand("../assets", __DIR__)
]
]
# ## SSL Support
#
# In order to use HTTPS in development, a self-signed
# certificate can be generated by running the following
# Mix task:
#
# mix phx.gen.cert
#
# Note that this task requires Erlang/OTP 20 or later.
# Run `mix help phx.gen.cert` for more information.
#
# The `http:` config above can be replaced with:
#
# https: [
# port: 4001,
# cipher_suite: :strong,
# keyfile: "priv/cert/selfsigned_key.pem",
# certfile: "priv/cert/selfsigned.pem"
# ],
#
# If desired, both `http:` and `https:` keys can be
# configured to run both http and https servers on
# different ports.
# Watch static and templates for browser reloading.
config :test_fourteen_bug, TestFourteenBugWeb.Endpoint,
live_reload: [
patterns: [
~r{priv/static/.*(js|css|png|jpeg|jpg|gif|svg)$},
~r{priv/gettext/.*(po)$},
~r{lib/test_fourteen_bug_web/views/.*(ex)$},
~r{lib/test_fourteen_bug_web/templates/.*(eex)$}
]
]
# Do not include metadata nor timestamps in development logs
config :logger, :console, format: "[$level] $message\n"
# Set a higher stacktrace during development. Avoid configuring such
# in production as building large stacktraces may be expensive.
config :phoenix, :stacktrace_depth, 20
# Initialize plugs at runtime for faster development compilation
config :phoenix, :plug_init_mode, :runtime
# Configure your database
config :test_fourteen_bug, TestFourteenBug.Repo,
username: "postgres",
password: "postgres",
database: "test_fourteen_bug_dev",
hostname: "localhost",
pool_size: 10
All standard from a normal phx_new call.
We really really need that SSCCE so we can just git clone ... it and run it ourselves.
