Isn’t localhost excluded from the “works only over https” limitation? At least that’s what I though would be the case.
LostKobrakai
chrismccord
Creator of Phoenix
1.4.0-rc.2 is out with updated plug dependencies, new Ecto 3.0 usec datetime support in our generators, as well as a few bug fixes.
To jump on the latest RC, first replace your :cowboy dependency with :plug_cowboy:
{:plug_cowboy, "~> 2.0"}
To upgrade to Cowboy 2 for HTTP2 support (which is the new default), use ~> 2.0 as above. To stay on cowboy 1, pass "~> 1.0".
Also, be sure to grab the latest rc.2 project generator:
$ mix archive.install hex phx_new 1.4.0-rc.2
Changlog below. Cheers,
–Chris
1.4.0-rc.2 (2018-10-20)
Enhancements
- [phx.new] Use Ecto 3.0RC, with
ecto_sqlin new project deps - [phx.new] Use Plug 1.7 with new
:plug_cowboydependency for cowboy adapter - [phx.gen.html|json|schema|context] Support new Ecto 3.0 usec datetime types
Bug Fixes
- [Routes] Fix regression in router compilation failing to escape plug options
- [phx.gen.json|html] Fix generator tests incorrectly encoding datetimes
- [phx.gen.cert] Fix generation of cert inside umbrella projects
21
dimitarvp
Just for the record, I had to do mix deps.update phoenix after applying the steps for jumping to RC2. (In case you tried upgrading after taking a nap like I did 
) Afterwards, mix do deps.get, compile succeeded.
0
oldpond
I could not get RC2 to work without plug_cowboy, and running “mix archive.install hex phx_new 1.4.0-rc.2”
returns this for me: phoenix 1.4.0-rc2 compile error · GitHub
I am working through B5 of the phoenix book, and the book is behind this change.
0
chrismccord
Creator of Phoenix
The archive install error is a bug in elixir that will be fixed in the next release. The workaround is to mix archive.uninstall phx_new before running the archive.install command. As you found, B5 lags the rc.2 release, so the plug_cowboy step is needed. Thanks for bearing with us, their shouldn’t be much left to need to deal with before final release.
6
oldpond
After changing {:cowboy, "~>; 1.0"} to {:plug_cowboy, "~> 2.0"}, I did mix deps.update --all and compile. This bumped cowboy to 2.5.0, cowlib to 2.6.0 and ranch to 1.6.2.
1
Gazler
Phoenix Core Team
bdarla
This change is present in 1.4-rc.2 when using the generator “mix phx.new <project_name>” but still missing when using “mix phx.new.web <project_name>”.
0
l00ker
Thanks for checking that.
I was upgrading Phoenix in an umbrella project which was originally generated with mix phx.new.web when I found that.
Was the {:jason, "~> 1.0"} dependency added to mix.exs by mix phx.new.web? If so, it could be a bug in the 1.4-rc.* phx.new.web mix task.
0
LostKobrakai
I’m wondering why the new onSync() callback for the presence API does not supply the updated presence object to the callback. Wouldn’t it be better to not have the callback need to depend on the object from outside the callback?
presence.onSync(() => do_something_with_presences(presence))
# vs.
presence.onSync(updated_presences => do_something_with_presences(updated_presences))
It probably makes not much difference as one needs to have the presence object at hand to attach the callback anyways, but I still prefer the latter to not need a closure and even though there is a object globally updating behind the scenes this feels like a more pure approach.
2