sashaafm

How to use the blogs section

You can post links to your blog posts either in one of the Official Blog Posts threads (like this one), or, via Devtalk.com. If you post via Devtalk we will automatically cross-post your blog post here in our Blog Posts section for each blog post (so one thread for each blog post) so long as you have an account with the same username and primary email address on both forums. We also remove the rel-nofollow attribute when your link appears on our homepage on Devtalk, so great for your SEO!

If posting via Devtalk be sure to:

Ensure your account on Devtalk.com has the same username and primary email as your account here
Initiate thread creation in one of the Blog Posts sections (for Elixir/Phoenix that may be in the Back End category, or for LiveView it could be the Front End category).
On thread creation paste the URL of your blog post in the TITLE field (once the URL appears in the body field below you can then change the title to whatever you like)
Include a short summary of your blog post then post the link on a separate line (here’s an example)
Include the Elixir and blog-post tags (as well as Phoenix, Nerves, LiveView etc if applicable)

It will then create a thread on Devtalk and then automatically cross-post here under your account

Edit: Please note you will need to be at TL1 over at Devtalk (usually takes about 15 minutes of browsing) for the link being pasted in the title bar to work - however if you PM @astonj he’ll manually bump you up to TL1

Please see this announcement for the full details: Calling all BEAM Bloggers!

131 comments

/phoenix #blog-posts #stickies #official-blog-posts-thread

15 26009 131

2026-04-15 05:49:48 UTC

First 10 of 131 Posts

AstonJ

Using Phoenix with docker (3 part series)

Post #1

sashaafm

Oh nice, I might need this for my Master Thesis

Post #3

AstonJ

Phoenix is modular - theerlangelist.com

…when I first looked at Phoenix, I was myself overwhelmed by the amount of concepts one needs to grasp. But after spending some time with the framework, it started making sense to me, and I began to see the purpose of all these concepts. I quickly became convinced that Phoenix provides reasonable building blocks which should satisfy most typical needs.

Furthermore, I’ve learned that Phoenix is actually quite modular. This is nice because we can trim it down to our own preferences (though in my opinion that’s usually not needed). In fact, it is possible to run a Phoenix powered server without a router, controller, view, and template. In this article I’ll show you how, and then I’ll provide some tips on learning Phoenix. But first, I’ll briefly touch on the relationship between Phoenix and Plug.

Post #4

AstonJ

Elixir Phoenix Deployment - jimmy-beaudoin.com

In this post, I’m going to explain how to deploy an Elixir Phoenix application on a VPS. We are going to use Elixir Release Manager (Exrm) for generating releases and all the necessary files to deploy our application.

Post #5

AstonJ

The path to Phoenix: Part 1 - Installing Node.js via nvm - verboseguides.com

Post #6

sashaafm

Using GenEvent to Notify a Channel of Updates in Elixir - learningelixir.joekain.com

Post #7

kiennt

Compare between Rails with cache and Phoenix without cache

http://sorentwo.com/2016/02/02/caching-what-is-it-good-for.html

Even the article does not describe details of environment of tests and data but its result is very interesting

Post #8

AstonJ

Nice find @kiennt - I was only just thinking what a pain caching can be - and in Rails we are spoilt because it probably has the best caching system of all the frameworks that can benefit from caching