If you have an interest in the Elixir ecosystem I think the Elixir Radar newsletter is useful resource. I followed it
even before I had any real opportunity to work with Elixir or Phoenix but it helped in keeping me up with conference
talks, interesting blog posts and assorted other stuff. I recommend it.
In the first part I covered the basics of
getting started with Dynamic repositories with Ecto. Using that post we can create one or more repos at runtime,
create the necessary database, run migrations to get it ready and then direct queries to it. That's a good start.
Building blocks for something better. I'll try to get into the better bits here.
You can listen to it here.
Ecto is the database library we know and love from the Elixir ecosystem. It is used by default in Phoenix, the
web framework. Ecto has a bunch of cool features and ideas. But this post is about a corner full of nuts, bolts and
very little of the shiny or hot stuff. It just covers some rather specific needs. Ecto docs for these features are
this guide and this API. But that is usually not the
whole picture. I'll try to cover some of the practicalities.
While I'm writing something a bit more involved and substantial I figured I could give an update on what I've been
doing. Mostly around Elixir. But I'll cover a few different things.
So I'm launching a newsletter. The sign-up is at the bottom of the page, it won't pop up here, so read on in
This is a post covering the creation and refinement of an open source project
within the Elixir ecosystem. More words than code. Be warned.
Whenever we design and create software we need to pay attention to the trade-offs we are making.
So I've been curious about what kinds of displays you can connect to the Pi-series single board computers for a
while. I happened to accidentally order a few. Among others an eInk display. I ordered the PaPiRus ePaper. It ended
up being dead on arrival and then out of stock so I received an Inky to replace it. Fair enough.
Me and nyaray finally finished up our work on the Inky eInk display library
to a level where we are happy to release it. So Inky 1.0.0 is now out on
Hex! Docs are on there too.
Do you have a system that is vital to your business that your development team seems to have given up on? Do they consider it old, slow, complicated or impossible to work with? Are they pushing heavily for a rewrite?
I’ve had Elixir on the brain recently. And by recently I probably mean 2 years. In my defense I think it is fair to say it is blooming right now. I haven’t had much need of it, or opportunity for it, in my day-to-day of maintaining a Python legacy system, renewing another legacy or optimizing Elasticsearch. So I’ve tried it with a few hobby projects I’ve spent time on and that was fun. But mostly I really just watched the community and what they did with a feeling of “Shiiiit, I want in on some of that!”. I'll primarily touch on BEAM, OTP, Phoenix Presence, Phoenix LiveView, Nerves, Scenic and Rustler.
This post covers setting up a Scenic project in the Elixir programming language. It briefly covers the default method
but largely dives into adding Scenic to an existing project, which covers the different parts that Scenic requires to