or subscribe with
Join 3,000+ readers for one email each week.
Digests » 232
Manning Publications is always looking to help developers grow. It doesn't matter what your background is, there's something for you to discover. This week, you can get 40% off your entire Manning.com order, including our range of Elixir books! Whether you're looking to pick up Phoenix or just improve your skills with the syntax, there's a way for you to boost your Elixir prowess.
this week's favorite
When you are hosting an Elixir/Phoenix app in DigitalOcean you may want to use Spaces, the DigitalOcean’s cloud storage alternative to AWS S3.
Learn how to leverage RabbitMQ along side Broadway to create a powerful data processing pipeline.
LiveComponents are a new feature of Phoenix LiveView, bringing lightweight reusable components into the LiveView ecosystem.
We had passing tests but in most test runs we had a big ugly Ecto sandbox warning because the test finished and terminated before the recording that the email was sent. Not great. Below is a simplified version of what that process looks like.
In a default Phoenix website, static assets are put in /priv/static in the file system, and will be served from / on the web. For example the CSS file at /priv/static/css/app.css will be served at /css/app.css. The problem this creates in my situation is that there's several folders for static assets (like /css and /js) which increases the chance of a path conflict with the old server.