zazaian

zazaian

Restructuring Phoenix 1.3-rc apps for 1.3.1, 1.3.2, 1.3.x

I recently generated the boilerplate for a new mix app using the Phoenix 1.3.1 phx.new generator and realized that the structure of the web directory and namespace have changed after 1.3-rc, which was structured differently than the 1.3.x release variants, namely 1.3.0, 1.3.1, and 1.3.2. Because I already had a production Phoenix app based on the 1.3-rc structure (upgraded from 1.2) running under the same umbrella, I wanted to update that app to match the structure of the formally released 1.3.x variants.

Fundamentally these changes are very simple:

  • The MyApp.Web module becomes MyAppWeb.
  • The top-level MyApp namespace no longer contains the OTP application configuration for the app. This privilege is now delegated to MyApp.Application.
  • Domain and web libraries are split apart in /lib as /lib/myapp and /lib/myapp_web.
  • Tests for myapp_web are moved into /test/myapp_web.

This might not sound like much, but many files will be affected and/or relocated. Here’s a high-level overview of my process for making these updates:

  • Use sed to update all references to the MyApp.Web module to MyAppWeb. Be careful not to include your git repo files when using sed destructively. I just grepped for the files containing MyApp.Web and sed-replaced them in batches per-directory with:
sed -i -e 's/MyApp\.Web/MyAppWeb/g' *.ex *.exs
  • Move your former /lib/myapp/web directory one level down, into /lib:
git mv lib/myapp/web/ lib/myapp_web
  • Move endpoint.ex from /lib/myapp to /lib/myapp_web:
git mv lib/myapp/endpoint.ex lib/myapp_web/endpoint.ex`
  • Move web.ex into /lib as the top-level MyAppWeb module definition:
git mv lib/myapp_web/web.ex lib/myapp_web.ex
  • Update the template root path in the new /lib/myapp_web.ex file to reflect the new directory structure:
# original 1.3-rc:
  def view do
    quote do
      use Phoenix.View, root: "lib/myapp/web/templates", pattern: "**/*",

# updated 1.3.x (1.3.0, 1.3.1, and 1.3.2):
  def view do
    quote do
      use Phoenix.View, root: "lib/myapp_web/templates", pattern: "**/*",
  • Move the application definition at /lib/myapp_web/myapp.ex to /lib/myapp/application.ex:
git mv lib/myapp_web/myapp.ex lib/myapp/application.ex
  • Update module name in the application file from MyApp to MyApp.Application:
# /lib/myapp/application.ex

# original 1.3-rc:
defmodule MyApp do
  use Application
  # ...
end

# updated for 1.3.x (1.3.0, 1.3.1 or 1.3.2):
defmodule MyApp.Application do
   use Application
   # ...
end
  • Update the application module name in mix.exs:
# /mix.exs

# original 1.3-rc:
  def application do
    [ mod: {MyApp, []},

# updated for 1.3.x (1.3.0, 1.3.1 or 1.3.2)
  def application do
    [ mod: {MyApp.Application, []},
  • Generate a new top-level module definition file at /lib/myapp.ex:
# This module was previous populated with the app code that we just extracted
# into MyApp.Application, so there isn't necessarily any additional code here unless
# you've added non-application code to the module:

# /lib/myapp.ex

defmodule MyApp do
end 
  • Update the live-reload patterns in your dev env config to reflect the changes. For example:
       # /config/dev.exs

       # original 1.3-rc
      ~r{lib/myapp/web/views/.*(ex)$},
      ~r{lib/myapp/web/templates/.*(eex|haml|slim|slime)$}

       # updated for 1.3.x (1.3.0, 1.3.1 or 1.3.2):
      ~r{lib/myapp_web/views/.*(ex)$},
      ~r{lib/myapp_web/templates/.*(eex|haml|slim|slime)$}
  • Move your web-related tests into /test/myapp_web. I previously had the tests for my views and controllers at /test/views and /test/controllers respectively, so I just moved them into a new myapp_web directory:
mkdir test/myapp_web
git mv test/views test/myapp_web
git mv test/controllers test/myapp_web

Finally I just updated the Phoenix version reference in mix.exs to 1.3.1 and did mix do: deps.get, compile, test, and everything worked correctly. I then took step further and updated my Phoenix dependencies to 1.3.2 and had no issues.

I believe this should be all of the necessary steps, but if I’ve missed anything, or any of this looks incorrect, please let me know and I’ll update the guide here.

Thanks,
Mike

Note: This post originally stated that this structual difference was a discrepancy between 1.3.0 and 1.3.1, when in fact it was a change made between the releases of 1.3-rc and 1.3.0. Thanks to @chrismccord for offering this clarification.

Most Liked

chrismccord

chrismccord

Creator of Phoenix

To be clear, we did not change any structure from 1.3.0 - 1.3.2. I believe you were running an early 1.3 RC version which used the App.Web namespace, and we moved to AppWeb before final release. I’ve updated the title accordingly :slight_smile:

zazaian

zazaian

Hey there Chris - thanks for the response here. That indeed was the case. I didn’t realize this structure had changed between 1.3-rc and 1.3.0. The clarification is much appreciated. I just quickly revised the references in the examples, but I’ll go through the tutorial tomorrow and update the rest of the language to better reflect this distinction.

Where Next?

Popular in Guides/Tuts Top

cheerfulstoic
I spent quite a bit of time trying to find a good configuration to build / test my Elixir app in CircleCI and then push an image to Docke...
New
mudasobwa
The post covering how to generate nifty types to use in @spec in compile time with macros. https://rocket-science.ru/hacking/2020/07/15/...
New
f0rest8
Hi everyone, Just wanted to say that the new Self-referencing many to many guide is now up on the official Hex docs (at least I just not...
New
nelsonic
Complete beginners Todo List Tutorial in Phoenix 1.5.3 (latest and greatest): It’s a feature complete TodoMVC clone with 0% JavaScri...
New
sergio
I couldn’t find any guides that worked well with Phoenix 1.6.0 and esbuild. I hope this helps people test the waters and eases you into t...
New
1player
A question I had when first learning contexts and Ecto was how to expand the default context API to support more flexible queries. Usuall...
New
OvermindDL1
Ran across this recently, it's a set of cheatsheet inforgraphic things of the OTP behaviours on the BEAM:
New
benwilson512
Correct if me I’m wrong, as best I can tell there aren’t any reasons to use mix run --no-halt in production vs releases. The marginal val...
New
AstonJ
This blog post hit my timeline earlier, and I’ve also been learning about some fantastic Elixir related tips via @pragdave’s new online c...
New
AstonJ
..or as and when you can think of one :icon_cool: This thread my also be of interest: What took you way too long to figure out? :003:
New

Other popular topics Top

fireproofsocks
I’m working on defining a simple Ecto schema for a table (in PostGres), but I don’t see where I can define a column as NOT NULL. Conside...
New
vonH
In asking this question I am more interested about the expressiveness of the language itself and less concerned about the availability of...
New
romenigld
I am trying to run a deploy with docker and I successfully runned with this command: docker build -t romenigld/blog-prod . but when I t...
New
New
mcarvalho
What is the difference between System.get_env and Application.get_env? For example, what are best practices to use one versus another.
New
ashish173
I am using Ecto timestamps with postgres, I can see the timestamps() use the :naive_dateime but for my use case I wanted to store the ti...
New
ovidiubadita
Hey all, I discovered Elixir and I love it. I always wanted to learn a functional programming and I intended to go for Haskell, but afte...
New
WestKeys
Currently suffering from paralysis by [HTTP client] analysis. This is rather unusual in Elixirland as there tends to be consensus on the ...
New
beno
I will often find my self writing things similar to: case some_value do nil -> something() "" -> something() _ -> someth...
New
magnetic
Hey :wave:t3: Elixir community, I’ve been learning Elixir, and working on some side projects. My editor of choice is VSCode, and althoug...
New

We're in Beta

About us Mission Statement