Building a Phoenix LiveView Native App
Note: This post reflects my experience working in LiveView Native before the recent (official) 0.3.0 release. I recently tried my hand at creating a…
Phoenix content on the Revelry Blog: Navigate our lab notes by using the tag system.
Note: This post reflects my experience working in LiveView Native before the recent (official) 0.3.0 release. I recently tried my hand at creating a…
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we…
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we…
At Revelry, we believe in sharing and learning from one another (beliefs that are rooted in our Core Values). Among the many things we do…
I recently had the opportunity to use Phoenix 1.7 and LiveView .18.3 in a production environment and it was, in a word, amazing. It’s…
Introduction One of the most handy features of Phoenix 1.6+ is the ability to use mix phx.gen.live to easily generate Liveviews, templates, and a…
You don’t have to forsake Elixir and Phoenix to work with Web3 and Blockchain. Liveview gives us the perfect intermediary. Background The Conference: The…
Elixir 1.9 has been released with built-in support for releases, a need that was previously served (and continues to be) by the Distillery package.
At Revelry, we are heavy users of DataDog so this solution leans heavily into putting metrics there.
Jason had a theory: He dislikes abbreviations and acronyms, ambiguity and magic. And he likes explicitness and clarity. So he wondered why some code naming conventions seem to punish verbosity (when it’s required) and what this all has to do with language naming conventions.