Phoenix and/or Bandit.
More accurately, Vancouver is built using Plug, so as long as your server supports that, you can use Vancouver.
Phoenix and/or Bandit.
More accurately, Vancouver is built using Plug, so as long as your server supports that, you can use Vancouver.
I’m still dragging it out albeit slowly with Phoenix Liveview. Slow and steady wins the race.
I made my first tutorial.
Hope it’s worth something to someone. ![]()
Background AI Translator in Ash Substack | Blog
Tutorial on how to trigger a background job (AshOban) to translate (LangChain) database fields and store them (AshTrans)
i am building a personal project for showcase
I am building a project that aims to be the gateway to the BEAM ecosystem:
This project will use Event Modelling with a mix of Event Sourcing and Event Driven, which are all new to me ![]()
I will build it in public and share my journey on LinkedIn.
Building a data warehouse (feel free to debate semantics of warehouses/data lakes if you can be bothered) with AWS Athena, Oban, and Phoenix liveview. Before that, wrote a data extractor/sync/backup to MS-SQL from teamwork.com. Yes, plenty of work getting done in elixir, just can’t be bothered blogging about it. Oban is a great tool btw.
working on my first saas
Working on a social app backend in Elixir, experimenting with multilingual support and AI integrations
@ken-kost kicked it of but today I spend some time further preparing the Igniter installer for Routex. The next release will do all code changes currently described in the Usage guide ![]()
Working through the Ash Framework book, while building as many apps as I can.
Looking for a job if anyone knows of anything ![]()
I am working on a framework composed of a set of libraries for low code Phoenix application development.
The first library is already published, and is the Aurora Ctx library, the second, and main one, is still in the oven. here is a draft documentation of the layout system for rendering and handling UI.
The framework scope (still a draft) is sketched here, and the libraries to implement (or not) will be considered later on.
Soon, I hope, Aurora Uix beta version will be published.
[1]Disclaimer: this is not like Ash Framework, it is aimed to provided a simple, yet powerful way to make Phoenix apps.
Footnotes ↩︎
I’m creating CSS library (Alos), but not yet open sourced. It used elixir to process design token from material.io.
I am finally launched an MVP of the site for travellers https://amotion.city
Here is an excerpt from the release notes.
AmotionCity is an innovative location-aware social platform that transforms how people discover, share, and interact with places around them. Built on cutting-edge Phoenix/Elixir technology, our platform combines the best of tourism assistance, community building, and professional tools into a single, powerful ecosystem.
For Tourists: Intelligent discovery of local points of interest with AI-powered route recommendations
For Communities: Robust foundation for location-based social interactions and content sharing
For Professionals: Comprehensive toolkit for tour guides, museums, and cultural institutions
If you are in Spain, Austria, or GB, and using Android phone, feel free to DM me with your email so that I could have you included in the internal testing program for the mobile app. Other regions come soon.
Hello guys,
I have made a Readers/Writer lock library please your feedback
Thank you
Finally giving Ash a second spin and coming to terms with it’s design.
@mhanberg Once made a visualizer for (h)EEx compilation, but it doesn’t work anymore with recent Phoenix. So working on a modernized version with Live preview (pun intended).
The naming still cracks me up. You would think the Tag Handler would be a Tag Engine, but you would be wrong.
@mhanberg maybe you can update the blog post once I finished the renewed visualizer?
Sure, you can also submit a PR to my blog, it’s on my GitHub.
Time to move on from this side-project, as I have bigger fish to fry. Still includes 1-on-1 copies of Mitch’ code, but now compatible with latest Phoenix and LiveView.
Other goodies
Todo (if you read this, maybe it your call…)
Next stop: Routex’s Example App
The burden of an extensible framework is answering the question “what can I do with it?”
In an attempt to at least have a shot at answering it, the current example app is being reworked in multiple pages. Each one showing a feature or use case.
Localize
Shows the values set, flashes the values that are updated on navigation and marks the values which are overridden.
Verified Routes
Has it’s own page
Better error messages and documented gotchas
In the process I also document the gotcha’s and improve the error messaging. Most gotcha’s are caused by LiveView’s optimizations making them easy to reason about and prevent in the future.
Found reason of issue: the infamous “don’t use in on_mount”
The reason some people were seeing this error message have been traced down to the new way Phoenix (LV) uses layout templates and the use of Verified Routes in layouts. The new method is meant to be more explicit, so we’ll have to be more explicit.
The new release will include better instructions how to change templates.
It also shows that 100% test coverage doesn’t not mean you catch all issues ![]()