I ran into a difference that I have not seen documented anywhere yet. Not sure if this is intentional @chrismccord ??
Generated new project on my headless dev machine (not my Mac host). When accessing the page at http://xxx.xxx.xxx.xxx:4000, the static assets could not be found. I had to change the Endpoint url host from “localhost” to “xxx.xxx.xxx.xxx”.
Is this intentional? If so, is it intentional?
elixir 1.7.3
phoenix 1.4.0-rc.0
I tracked down this problem to this pull request. The new layout template now includes full absolute URLs based on config instead of using relative paths.
This change also causes default css and js asset files to be served over HTTPS when user accesses the page through HTTP and HTTPS config is present (that’s what I had a problem with). Fortunately it’s just 2 lines to modify to change it back.
I think static_path makes the most sense for the default asset references. When folks go to deploy with a CDN, they can change the static calls as neccessary. I’m going to push rc.1 with some other fixes and will revert the linked PR. Thanks!
RC1 is out:
$ mix archive.install hex phx_new 1.4.0-rc.1
Existing apps on rc.0:
$ mix deps.update phoenix
Then bump your Phoenix Live Reload dep to 1.2.-rc: {:phoenix_live_reload, "~> 1.2-rc"},
.formatter.exs to hex package for proper elixir formatter integrationRoutes.static_url in app layout in favor of original Routes.static_path
Thanks Chris, A lot of love from Pakistan, Elixir (Phoenix) is the one programming language you cannot stay away or don’t love it.
New changes look nice, Congratulation on new release.
Just to avoid confusion for anyone else, if you’ve already installed rc.0, first uninstall it: mix archive.uninstall phx_new-1.4.0-rc.0.
Really excited about this. I’m just about to spin up a new project with phoenix at work, I’m I glad we can try to roll it out with 1.4!
Yes, great job Chris and company!!
I did some testing with Coherence and expected some issues. Really didn’t find any. Nice backwards compatibility.
I’m completely in line with you. There is a lot of cases where you wants to use the framework as it is, with enough functionalities to permit the development of a complete system, minimizing the amount of effort to find the packages required to complete the framework. Been there with Clojure 2 years ago. It was a pain to constitute a descend framework, analyzing dozen of optional packages. I went out of this world.
Phoenix offers the good parts of ruby on rails with easy swapping of functionalities when required.
Fantastic news! We’re doing our first ElixirHK tonight of the group reboot – so this is very good timing for us in addition to great timing for the Elixir community 
so exciting