I like the old way much more but I think I will put all new files inside Services directory and keep old style or rename accounts.ex to service.ex, from my point of view accounts/accounts.ex should stay outside the accounts folder, you can consider folders as namespaces.
lib/my_app
├── accounts
│ ├── user.ex
│ └── accounts.ex
├── sales
alexandrubagu@local:~/devel$ mix phx.new micro --umbrella --database mysql
alexandrubagu@local:~/devel/micro_umbrella/apps$ cd micr_umbrella/apps/micro_web/
alexandrubagu@local:~/devel/micro_umbrella/apps/micro_web$ mix phx.gen.html Accounts User users name:string
Yeah I did that, but as the contexts don’t go into the “non _web application”, I thought there might be another way.
There’s now an issue: Support a context_app: :foo configuration that will properly generate contexts in umbrellas · Issue #2139 · phoenixframework/phoenix · GitHub
It looks like generating a schema with a reference should be fixed in master but I’m still getting an error. Am I being derpy?
$ mix phx.gen.schema Blog.Post blog_posts title user_id:references:blog_users
* creating lib/hello_world/blog/post.ex
* creating priv/repo/migrations/20170303160218_create_blog_post.exs
Remember to update your repository by running migrations:
$ mix ecto.migrate
$ mix ecto.migrate
Compiling 1 file (.ex)
Generated hello_world app
08:02:23.215 [info] == Running HelloWorld.Repo.Migrations.CreateHelloWorld.Blog.Post.change/0 forward
08:02:23.215 [info] create table blog_posts
08:02:23.221 [info] create index blog_posts_user_index
** (Postgrex.Error) ERROR 42703 (undefined_column): column "user" does not exist
(ecto) lib/ecto/adapters/sql.ex:195: Ecto.Adapters.SQL.query!/5
(ecto) lib/ecto/adapters/postgres.ex:86: anonymous fn/4 in Ecto.Adapters.Postgres.execute_ddl/3
(elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
(ecto) lib/ecto/adapters/postgres.ex:86: Ecto.Adapters.Postgres.execute_ddl/3
(ecto) lib/ecto/migration/runner.ex:98: anonymous fn/2 in Ecto.Migration.Runner.flush/0
(elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3
(ecto) lib/ecto/migration/runner.ex:96: Ecto.Migration.Runner.flush/0
(stdlib) timer.erl:181: :timer.tc/2
(ecto) lib/ecto/migration/runner.ex:27: Ecto.Migration.Runner.run/6
(ecto) lib/ecto/migrator.ex:121: Ecto.Migrator.attempt/6
(ecto) lib/ecto/migrator.ex:71: anonymous fn/4 in Ecto.Migrator.do_up/4
(ecto) lib/ecto/adapters/sql.ex:615: anonymous fn/3 in Ecto.Adapters.SQL.do_transaction/3
(db_connection) lib/db_connection.ex:1274: DBConnection.transaction_run/4
(db_connection) lib/db_connection.ex:1198: DBConnection.run_begin/3
(db_connection) lib/db_connection.ex:789: DBConnection.transaction/3
(ecto) lib/ecto/migrator.ex:244: anonymous fn/4 in Ecto.Migrator.migrate/4
(elixir) lib/enum.ex:1229: Enum."-map/2-lists^map/1-0-"/2
(ecto) lib/mix/tasks/ecto.migrate.ex:84: anonymous fn/4 in Mix.Tasks.Ecto.Migrate.run/2
(elixir) lib/enum.ex:645: Enum."-each/2-lists^foreach/1-0-"/2
(elixir) lib/enum.ex:645: Enum.each/2
$
Haha yeah!
Just broken the 100-like mark 
I think one of the reasons people are so thrilled about this release because it shows just how self-assured Phoenix is and how it does not feel the need to ‘take over’ your entire app (as many other frameworks do). Instead it is doing everything it can to complement, support and strengthen Elixir. This kind of cohesion is just awesome and I think it really resonates with people 
In my experience I have found that Pragprog offer free upgrades unless it is a major rewrite of the book (usually in accordance with a major new version of the language/framework). But even that isn’t always strictly true (and is just a guess) - when I got Programming Ruby 1.9 they gave me PR2.0 free, when I got Agile Web Dev with Rails 3, they gave AWDWR 4 free. I don’t think I have ever paid for an upgrade tbh and I think this is one of the reasons why they sell so many more books than other publishers - many of us buy them knowing we want to read them at some point, rather than immediately, and are happy in the knowledge that we’ll probably get the latest version when we are ready for it (within reason).
Having said that, this is just a guess based on my experience - if in doubt email Pragprog.
