If you use Next.js as the reverse proxy to phoenix, does it mean that the static assets of the phoenix server would have to go through the reverse proxy?
If you make the vercel and flyio hosts use completely separate domain name, ie: mydomain.com for vercel, and app.mydomain.com and use full url for all the cross links, then the reverse proxy should not be necessary and everything should be a little faster, right?
Yes, static assets also get proxied through Vercel. But the speed difference is negligible.
That is the recommended way for splitting Static and Dynamic apps, but IndiePaper is a platform. Authors should be able to share their books URL as indiepaper.me/books/awesome-book-id rather than app.indiepaper.me/book/awesome-book. If I was building a simple SAAS, where the app is private and with no shareable links I would have gone with that.
Nicely written post 
Re: the purpose of optimize_boolean, to add the optimize_boolean: true flag to the AST’s meta here
[Disclaimer: I have practically 0 experience in metaprogramming and erlang, so read this with the phrase “it seems to me” in mind]
My curiosity then led me to read the erlang source code for expand_case where this flag is used. There it checks if the expression you’re branching on returns_boolean and if so optimizes the case depending on the shape of the true/false branches.
If the false branch matches the AST [{'when', _, [Var, {{'.', _, ['Elixir.Kernel', 'in']}, _, [Var, [false, nil]]}]}] then it rewrites the case clause to [false] and optimizes away the Kernel.in call, which is exactly what is sent to optimize_boolean from the code you analysed in the post!
In summary, if the if statement will return a boolean, then there’s no need to check for nil inclusion in the list with in/2.
Glad you liked it!
And thanks for sharing what you found re: optimize_boolean. I noticed it was setting the flag to true, but just wasn’t sure what the purpose of that flag was.
Makes sense that you’d want to get rid of Kernel.in if there’s no chance of nil being returned.
Newbie to Elixir but wrote a blog post about integrating with a pub/sub event broker: https://tkthetechie.io/event-driven-elixir/
Last year I wrote five part articles series - “Writing Git in Elixir” on medium.com.
Here are the links in case anyone is interested to read -
Building Git in Elixir — Part 1 (Initialize Repo & Store blobs) - https://itnext.io/building-git-in-elixir-part-1-2f2ec245df74?sk=b4ca6c7f4bbfd5b8f74785fc292e8657
Building Git in Elixir — Part 2 (Store Trees & Initial Commit) -
https://itnext.io/building-git-in-elixir-part-2-store-trees-initial-commit-9013ed02b75a
Building Git in Elixir — Part 3 (Make History & Store Executables)
https://itnext.io/building-git-in-elixir-part-3-make-history-store-executables-e7dbb39e8e47?sk=3a4f275892e3c4802f20b4b19abcb006
Building Git in Elixir — Part 4 (Store Nested Trees as Merkle Tree) -
https://itnext.io/building-git-in-elixir-part-4-store-nested-trees-as-merkle-tree-1a236882215a?sk=72d94cf323ba17d08c9580f6345d2e6f
Building Git in Elixir — Part 5 (Build Index) -
https://itnext.io/building-git-in-elixir-part-5-build-index-e10098836a83?sk=87cd1b215626b01909295704c3ce6bae
Thanks!
Hello, regardless of the current Neil Young vs. Joe Rogan controversy, it’s worth knowing that Spotify uses Phoenix LiveView to manage its artist ad platform. In my new article, I am writing about how Elixir and Phoenix rose from a proof of concept to the level of the actual game-changer, and what it takes to advocate for a particular technology to be employed by a huge company.
Enjoy!
