Summer of Elixir - podcast mini series

I just started listening to the Elixir Deployment podcast and noticed a mention about Google App Engine not supporting WebSockets (called sockets in the podcasts for some reason). This is already solved, see here: Elixir | Google Cloud Platform - #22 by stefanluptak
Anyway, I am currently trying to do the same CI/CD pipeline with GCP + Kubernetes, so I am really looking forward to the rest of that episode.

You beat me to the punch !!! Today’s episode is about that realization and transition to App Engine !!! Page not found

Continuing the Journey !!
Elixir with App Engine #86

App-Enggine WebSocket Support As of Feb 2019, it looks like we’re good to go. That coupled with the $30/month bill we would incur when our gcp credits ran out, this switch seems to make a lot of sense.

Excellent. Adding to my podcast queue.

We’ve finally getting into some of the actual Elixir now that our CI/CD is all set up and it’s a blast!!!
Checkout the progress, and look for the full rundown about it this week.

https://imgur.com/hJVbiwH

Jesse

Pretty sure I called them ‘sockets’ just of of laziness, good catch, kind of a big difference! I hope you got your pipeline up and running with GCP

We are making awesome progress !! Auth with Auth0 is totally working!!! Check it out

Elixir Phoenix with Auto0 #88

You can play with it at https://postit.blog

Trying to get my Phoenix deployment on GCP App Engine to force or redirect to the SSL connection. Currently you can connect to both http and https. I’ve seen a couple options

Using the app.yaml for gcp

//app.yaml
handlers:
- url: /.*
  script: auto
  secure: always
  redirect_http_response_code: 301

In the prod config using rewrite_on

config :postit, PostitWeb.Endpoint,
  http: [port: System.get_env("PORT") || 4000],
  # url: [host: "localhost", port: System.get_env("PORT") || 4000], # This is critical for ensuring web-sockets properly authorize.
  cache_static_manifest: "priv/static/cache_manifest.json",
  check_origin: false,
  server: true,
  root: ".",
  version: Application.spec(:postit, :vsn),
  rewrite_on: [:x_forwarded_proto]

Oh! So it looks like I am using the right value, but totally forgot the force_ssl part !

force_ssl: [ rewrite_on: [:x_forwarded_proto]]

I’ll try that and report back

Thank you! Great podcast on Elm. I put Elm on the back burner, but will look at it again.

Just fyi, we ended up setting up our pipeline with GitHub as a repo + pull requests → GitLab CI for CI, checks, etc. → Gigalixir for deployment. I would love to use GitHub Actions to avoid GitLab as another layer of complexity, but unfortunately, we’re still waiting for the public beta approval or for final release. As for Gigalixir, It’s lot easier to create, scale and mainly destroy an app compared to Google App Engine.