A common pattern in Ruby gem code is to have some sort of configuration file (ordinarily in YAML format) stored in a config directory of the gem. The gem then loads this with something along the lines of :
I built an administrative tool for my company that used Phoenix server side templating, bootstrap and datatables.js. This is not because I have an overwhelming preference for bootstrap or datatables.js. I just happened to find these first in the course of building the web app and they were able to solve my problem. Phoenix server-side templates are awesome, powerful and easy-to-use. I did have a bit of trouble with datatables so I figured I’d write up a brief blog post on how I got datatables to work with server-side paging.
I finally got to the point where I’ve developed something in Elixir and Phoenix that is actually useful for my company. Its a standard web site done in Phoenix. No fancy channel stuff for this. The problem I wanted to solve was to create a browser of internal relational database structures for our product. Stuff that just isn’t available through our UI but is always required by developers or operation folk when troubleshooting and involves fairly involved SQL. Instead of typing in lots and lots of different SQL you can now use this website and navigate to the problem through the links provided.
Sat down this morning and saw an interesting question on Elixir Ecto Slack channel :
Defining my own database schema for a simple Phoenix/Elixir project to present a company dashboard. I started with the following objects that I wanted to store in the relational database :