Phoenix removed support for http2 push before the release of 1.4 for reasons. It suggests Plug.Conn.push/3 as alternative.
LostKobrakai
1
ChaseGilliam
@SampsonCrowley yeah, that domain sadly expired and got scooped up while I was on vacation 
. But, I put the site back up under a new domain https://by-cha.se. As @LostKobrakai mentioned, push was removed from Phoenix, but you can accomplish the same thing with Plug.Conn.push/3.
That said, you can get the same effect with less work using a CDN like Cloudflare.
2
SampsonCrowley
@ChaseGilliam @LostKobrakai Thanks! I actually did find it while i was waiting for forum permissions by looking through the cowboy plug github
1
SampsonCrowley
I found out the hard way you actually don’t have to use webpack-dev-server to get this going in development either. Phoenix is capable of pushing the resource directly from the build. webpack-dev-server really caused a lot of headache because I could not figure out why it was still using 1.1; until i realized that it can’t support http/2 if you’re using node >= 11.1
test sample from my own codebase:
page_controller.ex
defmodule DownUnderSportsWeb.PageController do
use DownUnderSportsWeb, :controller
def index(conn, _params) do
push(conn, Routes.static_path(conn, "/js/shared-runtime.js"))
push(conn, Routes.static_path(conn, "/js/vendors~app.js"))
push(conn, Routes.static_path(conn, "/js/app.js"))
push(conn, Routes.static_path(conn, "/css/app.css"))
render(conn, "index.html")
end
end
this works for both development and production, because it uses the normal asset pipeline to find the same resources it would without proxying it through webpack
4
SampsonCrowley
@ChaseGilliam I think your original domain is back up for purchase if you wanted it back
Edit: nevermind, I think it’s only available through the people that scooped it up in the first place
0
ChaseGilliam
axelclark
Can anyone point me to a good resource for updating my Phoenix project to use HTTP/2? Thanks!
0
ChaseGilliam
axelclark