Phoenix 1.4.0 released!

phoenix-release

#1

Phoenix 1.4.0 released

Phoenix 1.4 is out! This release ships with exciting new features, most notably
with HTTP2 support, improved development experience with faster
compile times, new error pages, and local SSL certificate generation.
Additionally, our channel layer internals receiveced an overhaul, providing
better structure and extensibility. We also shipped a new and improved
Presence javascript API, as well as Elixir formatter integration for our
routing and test DSLs.

phx_new hex archive

The mix phx.new archive can now be installed via hex, for a simpler, versioned installation experience.

To grab the new archive, simply run:

$ mix archive.uninstall phx_new
$ mix archive.install hex phx_new 1.4.0

The new generators also use Milligram in favor of Bootstrap to support classless markup generation. The result is nice looking defaults that allow generated markup to be much more easily customized to your individual CSS requirements.

Note: Existing Phoenix applications will continue to work on Elixir 1.4, but the new phx.new archive requires Elixir 1.5+.

HTTP2

Thanks to the release of Cowboy 2, Phoenix 1.4 supports H2 with a
single line change to your mix.exs. Simply add {:plug_cowboy, "~> 2.5"}
to your deps and Phoenix will run with the Cowboy 2 adapter.

Local SSL development

Most browsers require connections over SSL for HTTP2 requests,
otherwise they fallback to HTTP 1.1 requests. To aid local development
over SSL, phoenix includes a new phx.gen.cert task which generates a
self-signed certificate for HTTPS testing in development.

See the Mix.Tasks.Phx.Gen.Cert docs for more information.

Faster Development Compilation

Our development compilation speeds have improved thanks to contributions to plug and compile-time changes. You can read more about the details in my DockYard post

New Development 404 Page

Our 404 page in development now lists the available routes for the
originating router, for example:

UserSocket connection info

A highly requested feature has been access to more underlying transport information when using Phoenix channels. The 1.4 release now provides a connect/3 UserSocket callback, which can provide connection information, such as the peer IP address, host information, and X-Headers of the HTTP request for WebSocket and Long-poll transports.

Deprecated Transport macro

As part of the channel overhaul, we have deprecated the transport macro, in favor of providing transport information directly on the socket call in your endpoint. Updating is easy, by making the following changes:

# app_web/channels/user_socket.ex
- transport :websocket, Phoenix.Transports.WebSocket
- transport :longpoll, Phoenix.Transports.LongPoll, [check_origin: ...]

# app_web/endpoint.ex
- socket "/socket", MyAppWeb.UserSocket
+ socket "/socket", MyAppWeb.UserSocket, 
+   websocket: true # or list of options
+   longpoll: [check_origin: ...]

New Presence JavaScript API

A new, backwards compatible Presence JavaScript API has been
introduced to both resolve race conditions as well as simplify the
usage. Previously, multiple channel callbacks against
"presence_state and "presence_diff" events were required on the
client which dispatched to Presence.syncState and
Presence.syncDiff functions. Now, the interface has been unified to
a single onSync callback and the presence object tracks its own
channel callbacks and state. For example:

let presence = new Presence(roomChannel)
presence.onSync(() => {
  console.log("users online:", presence.list((id, {name}) => name))
})

That’s all there is to it!

webpack

The mix phx.new generator now uses webpack for asset generation instead of brunch. The development experience remains the same – javascript goes in assets/js , css goes in assets/css , static assets live in assets/static , so those not interested in JS tooling nuances can continue the same patterns while using webpack. Those in need of optimal js tooling can benefit from webpack’s more sophisticated code bunding, with dead code elimination and more.

Programming Phoenix Book

The Programming Phoenix Book
is in beta and available through PragProg, and includes all the latest changes for 1.4.
We have titled the book “>= 1.4” and consider it relatively future proof as we continue
minor version releases.

Special Thank You’s

We would like to specially thank Loïc Hoguin for his work on Cowboy 2,
allowing us to provide a first-class HTTP2 experience. We would also like
to thank Bram Verburg, who contributed the local SSL certificate generation,
for cross-platform, dependency-free cert generation.

Additionally, I would like to thank José Valim and Plataformatec for their work on the channel layer overhaul which provides an extensible foundation going forward.

As always, we have provided step-by-step instructions for bringing your 1.3.x apps up to speed:

Please report issues to the issue tracker, and find us on
#elixir-lang, elixir slack, and the Elixir forum if you have any
questions. The full list of changes from the changelog can be found below.

Happy hacking!

–Chris

Enhancements

  • [phx.new] Update Ecto deps with the release of Ecto 3.0 including phoenix_ecto 4.0
  • [phx.new] Import Ecto’s .formatter.exs in new projects
  • [phx.new] Use Ecto 3.0RC, with ecto_sql in new project deps
  • [phx.new] Use Plug 1.7 with new :plug_cowboy dependency for cowboy adapter
  • [phx.gen.html|json|schema|context] Support new Ecto 3.0 usec datetime types
  • [Phoenix] Add Phoenix.json_library/0 and replace Poison with Jason for JSON encoding in new projects
  • [Endpoint] Add Cowboy2Adapter for HTTP2 support with cowboy2
  • [Endpoint] The socket/3 macro now accepts direct configuration about websockets and longpoll
  • [Endpoint] Support MFA function in :check_origin config for custom origin checking
  • [Endpoint] Add new :phoenix_error_render instrumentation callback
  • [Endpoint] Log the configured url instead of raw IP when booting endpoint webserver
  • [Endpoint] Allow custom keyword pairs to be passed to the socket :connect_info options.
  • [Router] Display list of available routes on debugger 404 error page
  • [Router] Raise on duplicate plugs in pipe_through scopes
  • [Controller] Support partial file downloads with :offset and :length options to send_download/3
  • [Controller] Add additional security headers to put_secure_browser_headers (x-content-type-options, x-download-options, and x-permitted-cross-domain-policies)
  • [Controller] Add put_router_url/2 to override the default URL generation pulled from endpoint configuration
  • [Logger] Add whitelist support to filter_parameters logger configuration, via new :keep tuple format
  • [Socket] Add new phoenix_socket_connect instrumentation
  • [Socket] Improve error message when missing socket mount in endpoint
  • [Logger] Log calls to user socket connect
  • [Presence] Add Presence.get_by_key to fetch presences for specific user
  • [CodeReloader] Add :reloadable_apps endpoint configuration option to allow recompiling local dependencies
  • [ChannelTest] Respect user’s configured ExUnit :assert_receive_timeout for macro assertions

Bug Fixes

  • Add missing .formatter.exs to hex package for proper elixir formatter integration
  • [phx.gen.cert] Fix usage inside umbrella applications
  • [phx.new] Revert Routes.static_url in app layout in favor of original Routes.static_path
  • [phx.new] Use phoenix_live_reload 1.2-rc to fix hex version errors
  • [phx.gen.json|html] Fix generator tests incorrectly encoding datetimes
  • [phx.gen.cert] Fix generation of cert inside umbrella projects
  • [Channel] Fix issue with WebSocket transport sending wrong ContentLength header with 403 response
  • [Router] Fix forward aliases failing to expand within scope block
  • [Router] Fix regression in router compilation failing to escape plug options

phx.new installer

  • Generate new Elixir 1.5+ child spec (therefore new apps require Elixir v1.5)
  • Use webpack for asset bundling

Deprecations

  • [Controller] Passing a view in render/3 and render/4 is deprecated in favor of put_view/2
  • [Endpoint] The :handler option in the endpoint is deprecated in favor of :adapter
  • [Socket] transport/3 is deprecated. The transport is now specified in the endpoint
  • [Transport] The transport system has seen an overhaul and been drastically simplified. The previous mechanism for building transports is still supported but it is deprecated. Please see Phoenix.Socket.Transport for more information

JavaScript client

  • Add new instance-based Presence API with simplified synchronization callbacks
  • Accept a function for socket and channel params for dynamic parameter generation when connecting and joining
  • Fix race condition when presence diff arrives before state
  • Immediately rejoin channels on socket reconnect for faster recovery after reconnection
  • Fix reconnect caused by pending heartbeat

When is Phoenix 1.4 going to be released?
Elixir alliances - with who?
When is Phoenix 1.4 going to be released?
1.4.0.rc1 SSL issue related to loading / using certs
#2

#3

Whoo hoo - well done Chris and everyone else involved!! :041:

Can’t recommend this book highly enough!! :049:


#4

One of the best things to read about that is the >= 1.4. Just knowing that there’s not going to be an expectation of buying a new book everytime a new version comes out is pretty fantastic.


#5

Hi! This is awesome, thanks to everyone for their hard work on this!

I remember watching a talk a while back, given by Chris McCord I think, saying that providing better instrumentation/metrics primitives for services like AppSignal, New Relic, etc., to build on. Did that get dropped?


#6

Are you referring to the telemetry project?


#7

Telemetry is what that project became. Chris mentioned it in his talk at elixirconf but it got a little pushed aside by the LiveView thing.


#8

Agreed!

And I would wager that @chrismccord will be happy if he doesn’t need to write a new book every time a new version of Phoenix comes out as well, considering the amount of work involved :sweat_smile:

Seconded! It’s a great book. Everyone should have a copy readily available.


#9

That’s the one! We will fully integrate it on Phoenix v1.5. Ecto 3.0 will already leverage Telemetry though.


#10

I thought the telemetry library was meant to be in Erlang so that it is easier for the entire BEAM ecosystem to take advantage of it?


#11

Observation:

$ mix phx.gen.cert
* creating priv/cert/selfsigned_key.pem
* creating priv/cert/selfsigned.pem

If you have not already done so, please update your HTTPS Endpoint
configuration in lib/_web/config/dev.exs:

  config nil, Web.Endpoint,
    http: [port: 4000],
    https: [
      port: 4001,
      certfile: "priv/cert/selfsigned.pem",
      keyfile: "priv/cert/selfsigned_key.pem"
    ],
    ...

# ...a word of warning follows, not copy-pasted...

Aside from the nil in the config snippet which is easy to catch (but should still be fixed), I had a slight WTF actually pointing my web app to the generated self-signed certificates. They rest comfortably in my $UMBRELLA_ROOT/priv/cert/ directory and me copy-pasting the above snippet in apps/myapp_web/config/dev.exs is looking for them in $UMBRELLA_ROOT/_build/dev/lib/myapp_web/priv/cert/selfsigned_key.pem. OK, I just move them to apps/lib/myapp_web/priv/certs/ and recompile. The local SSL listener works.

The generator should probably be umbrella-aware when offering help. It was easy to fix the error but I imagine it would catch off-guard somebody who is in a rush.


#12

How would this piece of code be affected by the deprecation on view as an argument to render?

<div class="row">
  <div class="col-md-12">
    <%= render(SharedView, "_pagination.html", path: public_skill_path(@conn, :index), pagination: @pagination) %>
  </div>
</div>

#13

unchanged, we only deprecated the Phoenix.Controller.render which accepts a view, in favor of conn |> put_view |> render(...)


#14

Milligram seems dead. You just switched from brunch to webpack, but had to take in another dead dependency? The fact that its installation instructions still includes bower… And it still has clearfix… And its last commit was half a year ago, so its grid system implementation is most likely outdated… I don’t use that part of Phoenix, but felt strongly that it needs to be pointed out.


#15

First off, Milligram is tiny. The big goal is for all of our generated markup, whether phx.new or phx.gen.html, is to be classless, while still looking great out of the box. Milligram gives us that. We’re not prescribing you use Milligram for all your styles, rather we are allowing folks to hit the ground running and not have to rewrite all their HTML later when they go to use Bootstrap, foundation, Bulma, et al, or their own custom CSS solutions.


#16

classless is a good idea. Thanks!


#17

Ah I misunderstood. Thanks!


#18

Good job, Is there a specific schedule for rc1 or any other rc.x?


#19

Anyone else excited that this means LiveView is one step closer? :048:


Phoenix LiveView Info
#20

Excited? Very much so – I can’t wait! However, I doubt we will see LiveView any time in the near future :face_with_raised_eyebrow: