Qqwy
Update:
How to use the Blogs & Podcasts section
You can post links to your blog posts or podcasts either in one of the Official Blog Posts threads (like this one) or the Elixir Podcasts thread, or, if yo want a dedicated thread for each blog/podcast, via Devtalk.com. If you post via Devtalk we will automatically cross-post your blog post here in this section for each blog post or podcast (so one thread for each) 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/Podcasts sections (for Elixir/Phoenix that may be in the Back End category, or for LiveView it could be the Front End category).
- Make sure the last link in your post is to your blog post as this is the link that will get featured on Devtalk (You can however override this by pasting the URL of your blog post or podcast in the TITLE field, however you will need to be at Trust Level 1 to do that.)
- Include a short summary of your blog post or podcast then post the link on a separate line (here’s an example)
- Include the
Elixirandblog-post(orpodcast) tags (as well asPhoenix,Nerves,LiveViewetc if applicable). Don’t include the tags forErlangor any other BEAM language as the system will instead post your blog post on to the Erlang Forums.
It will then create a thread on Devtalk and then automatically cross-post here under your account ![]()
Please see this announcement for the full details: Calling all BEAM Bloggers!
![]()
This thread exists to aggregate learning resources about Elixir.
Feel free to add links to blog posts, articles, screencasts, etc. to the Wiki (this post) as well as in a new post in the thread (so everyone else is alerted as well) ![]()
Introductions to Elixir
Elixir - First steps · trydis
The Elixir of Concurrency
Thoughts on ElixirConf 2016
Why we choose Elixir as the main technology for our startup?
Elixir in comparison to
Functional Programming is not weird: you just need some new patterns — Medium
Why I’m betting on Elixir — Medium
How Elixir’s Ecto differs from Ruby’s ActiveRecord
Why We Choose Elixir To Power Our SMS Infrastructure - PortaText
Elixir: The most Object-Oriented Language
Two million web servers
Beyond functional programming with Elixir and Erlang
Data Structures
Elixir Arc with a single module
Design Patterns
CQRS with Elixir and Phoenix
The Most Object-Oriented Language
Concurrency & OTP
Introduction to Elixir Processes
Ramblings of a Geek: Let’s Build Something: Elixir, Part 1 - A Simple GenServer
Ramblings of a Geek: Let’s Build Something: Elixir, Part 2 - Supervising Our GenServer
Understanding State with Elixir Agents — Automated Solutions
Pub/Sub in 30 Lines of Elixir — NoRedInk Tech
Creating Elixir libraries as OTP applications
Understanding Exit Signals in Erlang/Elixir
Pi Calculation with Elixir
:ets
Taming :ets for High-Performance Software
Metaprogramming/Macros
Getting Started with Elixir Metaprogramming
The Erlangelist - Understanding Macros
Testing
Ramblings of a Geek: Let’s Build Something: Elixir, Part 3 - Getting Started with ExUnit for Testing
Ramblings of a Geek: Let’s Build Something: Elixir, Part 4 - Better Tests, TypeSpecs, and Docs
Debugging
Debugging techniques in Elixir « Plataformatec Blog
How to trace Elixir nodes with Erlyberly « Plataformatec Blog
Elixir+Elm
note: We have a special place for Elm-related resources here.
Are Elixir and Elm the Perfect Couple?
Tomasz Kowal - Elixir and Elm - the perfect couple (Lambda Days 2016) - YouTube
Elixir Internals
Elixir RAM and the Template of Doom
The Erlang Garbage Collector
Web
note: We have a special place for Phoenix-related resources here.
Simple Web Servers with Plug and Cowboy
Ways to use Elixirscript Today
Ecto - the Past, the Present, the Future
Increasing SSL Security in Erlang/Elixir
Elixir Application with Ecto “Mix Elixir project with Ecto” @prio_mahabub
Artificial Intelligence
Coding A.I. Techniques in Elixir: The Generate and Test Algorithm — Automating The Future
Mix
Elixir 1.1 mix profile.fprof command
Ecto
How to use data spanning multiple data sources in Elixir
Deployment
How Honeybadger Uses Elixir To Monitor Heroku
Continuous Delivery for Elixir, Part 1: Introduction
Integration with 3rd party applications
Building a bot for Facebook Messenger, using Elixir
Setting up simple Live Chat in a Phoenix project using Planga
Short Tips
HMAC in Elixir and Python · My Random Thoughts
TIL: Elixir can pattern match at multiple depths in a single statement
Using Functions in Elixir Guard Clauses
Types
Type Checking in Elixir
Type-checking and spec-testing with TypeCheck
Trending in Blog Posts
Other Trending Topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #performance










Showing Posts 441 to 450- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
petecorey
I put together a new post in my “literate commits” style where I go about building the simplest possible Phoenix application from the ground up, one commit at a time.
Check it out: Minimum Viable Phoenix
I’m pretty excited about this format, and I’m interested to know what people think!
rozerosie
Configuring Distillery
Latest post from Eric over at the SmartLogic blog:
“Following up on our last post about generating an Erlang release through Docker, let’s talk about how we configure Distillery to generate the actual release. Here again I’m using the example of the scripts I use to deploy Grapevine, to give us a real example to look at.”
OvermindDL1
These are always fun ones to read! ^.^
EDIT:
No clue what a
.DS_Storeline is doing in your.gitignorefile or what it is for? I don’t see it listed in any of my .gitignore’s that I’ve grabbed from a large variety of git projects. Should detail why it is there and what it has to do with Elixir?griffinbyatt
DS_Store is a macOS file that contains folder information. Usually included in global gitignore files!
OvermindDL1
Ah, yeah, system-specific junk files like the macos stuff should not go in project
.gitignorefiles, that’s like the Windows icon cache file litter too which that post left out in that case. Should set that globally by putting it in a global gitignore file, likeecho .DS_Store > ~/.gitignore_globaland make sure git uses it as the global gitignore viagit config --global core.excludesfile ~/.gitignore_global.sorentwo
Hmm. I thought git respected a .gitignore in the home folder by default. I have a few things in there (TODO, .DS_Store) and don’t recall ever setting anything in the config.
OvermindDL1
Hmm, it wasn’t on any of my systems… Let me check the help file. ^.^;
Ooo, I’m very sure it used to not have a default, but now apparently the default is
$XDG_CONFIG_HOME/git/ignorefalling back to$HOME/.config/git/ignore.hauleth
Today I have found this article:
Enjoy.
michallepicki
Love the format. Each section is a commit. You can clone the repo and go through the post using git and run the commands yourself, while reading the blog post in your terminal git history.
It would be awesome to have a similar thing that would be runnable as a test. I would embed commands with expected output. If the output doesn’t match, the test fails. Integrate it into
ex_doc. No more outdated “soft” documentation, like Phoenix guides.marciol
@petecorey published it on Elixir Blog Posts. This is a really interesting article and reminds me of a friend that started over a very simple project in which he used only Plug, but after some time he discovered that he was reinventing Phoenix, so he dropped to regular Phoenix.