PaperTrail VS Avo

if the source (web) application makes their own audit tables. ex: our ruby on rails application uses the paper-trail gem

Start with https://github.com/paper-trail-gem/paper_trail

We use paper_trail for this

I think you could use that in conjunction with the paper_trail gem, as /u/GreenCalligrapher571 mentioned, which is also a good suggestion. As an additional note, when changing records in production while using the paper_trail gem, I suggest wrapping your database-mutating statements executed in the rails console within a whodunnit block, so PaperTrail.request(whodunnit: 'Dorian Marié') { widget.update name: 'Wibble' } or something rather than just widget.update name: 'Wibble'. Or, if you have some sort of issue-tracking / ticketing system, you could set the whodunnit value to the ticket number or whatever, and then anyone who wants to know why the records are in the state they're in can consult that ticket, which hopefully has additional relevant context.

For a while we did this using the paper-trail gem. This was a very simple way to add a few lines of code to keep track of all of the changes made to an ActiveRecord model. But it came with one drawback. Every change to the data had to be done through ActiveRecord. There are often times when this makes an app vulnerable to a race condition. I’ll use a contrived example so as not to share any real code from our client’s app.

In most designs, this would probably not be possible unless a table tracking extension is being used in an ORM. Even with change tracking enabled through extensions like paper trail or Django simple history, it can be tricky to restore deleted entities. Object tracking would need to have been enabled before it is needed to ensure the data is still around to be restored.

Maybe you are looking for the papertrail gem? https://github.com/paper-trail-gem/paper_trail

Quality is often much better with these kinds of templates and frameworks, because the creators often can make better default choices.

For example, Avo (https://avohq.io) and Bullet Train (https://bullettrain.co/) are IMHO both much higher quality out of the box than what a typical intermediate Rails developer could accomplish in months of full time learning and coding.

<%= link_to(@car) do %> <%= @car.name %> -- Check this car! <% end %> cars/1"> Tesla -- Check this car! <%= link_to "https://avohq.io/" do %> AvoHQ - The Best Rails Guide <% end %> https://avohq.io/"> AvoHQ - The Best Rails Guide

Access the Avo, and click on Sign Up. After completing registration, click on your profile icon and select Subscriptions, then Choose a plan, choose the Pro version and click on Start 30 day trial. The system URL is not required, click Subscribe. Now you will have your key to use the Avo 2 Pro version for 30 days.

But there's another alternative for Ruby on Rails. This is a shameless plug, but why don't you try Avo?

URL: https://avohq.io

Nothing really beats Rails. Use something like Jumpstart (jumpstartrails.com) and Avo (https://avohq.io) and you scaffold a full consumer-ready app in literally a few hours.

The thing that bugs me the most with Next.JS and the whole JAMStack movement is that, yeah, you get from "git clone" to deployed on Vercel in two minutes, but if you need to create real app features like a sturdy admin, accounts, authorization, proper asset management, CI/CD, it takes a whole lotta time. I'm not even touching the most common app features.

Hey. I'm Adrian, author of Avo. Avo is similar to Refine but for Ruby on Rails.

It helps developers create CRUD-like applications such as internal tools, admin panels, Content Management Systems and user-facing apps.

I love seeing more and more movement in this space.

https://avohq.io

Laravel has Nova, Django has Django Admin, and now, Rails has Avo.

https://avohq.io

*I am the author of Avo