brick VS phlex

(While you were doing this article, I've been busy making bugfixes on the gem that looks at a database and auto-creates migrations.)

I'm on a path to try to recreate the Django admin interface in Rails. Many things work -- all BT and HM things, plus polymorphism / STI stuff / etc. And it's fast. But it doesn't yet have time series stuff or some other niceties that the Django one does.

Working VERY hard to have a lean and mean admin panel that can compare favorably to Django's.

Was able to fix that bug in the video when the ERD diagram had two lines when there should have been only one. So creating this example ended up revealing that bug and now has made The Brick that little bit stronger.

Using The Brick is an easy way to make many Rails 3.1 apps run under Ruby 2.7.8. In your Gemfile: gem 'brick' And at the very top of your application.rb add this line: require 'brick' And there's a good chance it will run fine. Note that nothing older than 3.1 will work. You got lucky to have an app that's right at the cutoff line!

I feel your pain, u/2called_chaos -- so much that after being totally fed up with this kind of unreliable faff, I fixed it in a gem I maintain! Here's a video demo of your exact setup. You can see it broken and then working after simply adding the gem:

-Lorin Curator of The Brick.

... and while waiting, unrelated, but if you haven't yet given my lockdown creation a whirl then please drop this into your current project and tell me what you think -- a gem called The Brick!

For the full story on auto-creating RESTful APIs for any Rails app, [go here](https://github.com/lorint/brick).

I want to bring 👽 my API thing 🚀 to your martian party with hopes that it could become a useful player amongst your universe of useful gems!

The community was a delight! I can't even count how many people I connected with, and it was just great to meet people whom I had previously only interacted with online. Also got to meet a lot of those people who significantly contribute to the Rails ecosystem. Everyone I said hi to was more than willing to spare time and nerd out and share experiences. I was also thrilled to connect with Philip, who shares my enthusiasm for Phlex. He provided me with some exciting ideas for creating an even more crazy yet cohesive form object with Phlex.

Why use ActiveAdmin or RailsAdmin: Brick is not nearly as configurable -- at least yet! With Brick you can drop in your own model / controller / view template and it will use it, but on its own you can not change theming / use it to do templating tricks / etc. Currently working hard to arrive upon a straightforward and logical approach so that all of this will be possible. Looking into Arbre (used by ActiveAdmin) and Phlex for inspiration.

Phlex is an incredibly refreshing gem created by Joel Drapper. It introduces a remarkable way to build views in pure Ruby, as exemplified below:

A few months ago I came across https://www.phlex.fun and thought it was a nifty little library that could be useful for creating components. Since then I've been playing around with it in Rails, using it more seriously, and finally took it to a point where I built a Rails application with 100% Phlex components and 0% Erb. The other crazy thing is I figured out how to inline the Phlex view components into a controller, so prototyping Rails apps feels vaguely familiar to prototyping one in Sinatra.

A colleague has been using Phlex and I’ve since tried it as well. For me having it all be straight ruby, in one file, has worked and just from my personal preference something I’ve enjoyed over view_components.

phlex

You might want to take a look at Phlex, which essentially has the same syntax: https://github.com/joeldrapper/phlex