aisukuma

aisukuma

Hello all, I just got a new work station and have been trying to set up a new Phoenix Project for an app I’m working on. However I’m running into an issue that I haven’t seen before. I’m able to run ‘mix phx.new hello’, but after I ‘cd hello’ and try to run any mix command, I get the following error:

$ mix
.exsCode.LoadError) could not load /Users/htran/Desktop/hello/config/dev
(elixir) lib/code.ex:1147: Code.find_file/2
(elixir) lib/code.ex:706: Code.eval_file/2
(mix) lib/mix/config.ex:187: anonymous fn/2 in Mix.Config.import!/2
(elixir) lib/enum.ex:1925: Enum.“-reduce/3-lists^foldl/2-0-”/3
(mix) lib/mix/config.ex:186: Mix.Config.import!/2
(stdlib) erl_eval.erl:680: :erl_eval.do_apply/6
(elixir) lib/code.ex:232: Code.eval_string/3

Following the installation guide, I’ve already installed Elixir, Erlang, Phoenix, Node and Postgresql. Is there anything I’m missing?

Not sure if this is relevant but this is my ‘mix -v’

Erlang/OTP 21 [erts-10.1.3] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:1] [hipe] [dtrace]

I wasn’t getting this kind of error on my previous work station, so I’m thinking I missed a prerequisite or something. Thanks in advance!

Showing Posts 1 to 10

chensan

chensan

Is there anything wrong with your dev.exs file?

aisukuma

aisukuma OP

I haven’t touched my dev.exs file, do I need to add anything to it? This is what it looks like:

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 :hello, HelloWeb.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 :hello, HelloWeb.Endpoint,
  live_reload: [
    patterns: [
      ~r{priv/static/.*(js|css|png|jpeg|jpg|gif|svg)$},
      ~r{priv/gettext/.*(po)$},
      ~r{lib/hello_web/views/.*(ex)$},
      ~r{lib/hello_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 :hello, Hello.Repo,
  username: "postgres",
  password: "postgres",
  database: "hello_dev",
  hostname: "localhost",
  pool_size: 10

Sorry if I’m asking anything trivial, this is actually my first time setting up a Phoenix Project by myself.

yurko

yurko

Maybe it’s trying to find a secret part of a config? Look for something like import_config "dev.secret.exs".

aisukuma

aisukuma OP

I have the import_config "dev.secret.exs" line in my prod.exs file, but not in my dev.exs file

chensan

chensan

Which phoenix version do you have?

$ mix phx.new --version

How about recreating your hello project? It should just works fine out of the box.

yurko

yurko

that can’t be right :slight_smile: Try to generate a completely new project in another dir and see if it works

aisukuma

aisukuma OP

Phoenix version:

$ mix phx.new --version
Phoenix v1.4.0

I’ve tried several times to create the hello project following the Up and Running guide, I actually just tried again and am still getting the same error.

I’m also on a Mac if that’s relevant at all

aisukuma

aisukuma OP

Where should the import_config "dev.secret.exs" line be located?

I also just tried to create the project in a different directory and I’m getting the same error, import_config "dev.secret.exs" is also still in the same place.

yurko

yurko

It should be in the dev config, prod might have its own secret. Try to kill your generator and install it again. Something like mix archive.uninstall phx.new and then mix archive.install hex phx_new 1.4.0.

yurko

yurko

I just generated a project and see that only prod has a secret and it’s prod.secret: import_config "prod.secret.exs", dev should just work out of the box.

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews