I had a conversation with Marko Budiselić, the CTO at Memgraph, during this year’s DORS/CLUC conference. We discussed graph databases in detail and explored their capabilities and applications. Since I had no prior experience with graph databases, I found the discussion fascinating. As an enthusiastic user of Elixir, I was especially curious about the possibility of integrating Elixir with Memgraph and using its features within the Elixir ecosystem.
This week I got a very weird bug report - the API action was not saving an update to the record with a user with limited rights. For this example let’s say that this role can only change the value of a record and not anything else. Frontend will always send all params of a record but only the value will change.
When all you need is a quick way for validation Phoenix params (either query or body) sometimes including a library1 is too much, especially for smaller projects. Today I’m going to go thru a very simple way of creating a validation schema, using it in a controller, and rendering the error in the view. None of the ideas in this post are really new2 but I didn’t find a full write up of this approach.
I run a couple of internal and public applications written in Phoenix on our infrastructure. While services like fly.io exist and are amazing, sometimes it’s both cheaper (and more secure) to run small internal applications on your own hardware. It’s certainly more fun. Thru the years I’ve developed my own process of deploying the application and this post will document the current procedure.
Currently elixir-ls dialyzer does not work with OTP 25 and you can either downgrade to OTP 24 and wait for the fix, or build your own version of vscode-elixir-ls.
Slides to the talk I gave at Elixir Zagreb user group are here in PDF format. Thanks for coming to my ted talk and watch this space for corrections and other notes as well! See you in September!