/explore
|
You are here 
|
akoutmos.com | ||
| | | | |
minhajuddin.com
In a previous blog post I was trying to store username/email in a case insensitive way in postgres. A few folks commented that the citext postgres extension actually did this in a very easy and straig |
|
| | | | | ||
| | | | |
bryananthonio.com
A step-by-step guide on creating a REST API with Phoenix, covering everything from database setup to endpoint implementation. |
|
| | | | | ||
| | | | |
blog.nootch.net
Posts in this series Part 0 Part 1 Part 2 Part 3 Part 4 Part 5 Part 6 Part 7 Onward In the previous articles, we went over installing the tools we'll need for our API project and a small introduction to Event Sourcing, DDD and CQRS and how our library of choice, Commanded, interprets them. We aim to develop a simple Banking API that allows for: |
|
| | | | | ||
| | | | |
fullstackphoenix.com
Let say you app uses a javascript library that needs to interact with your app. For example a LiveView component. That is possible with the built in Phoenix Channels and Phoenix PubSub. |
|
| | | |||
