PaperTrail
Track changes to your rails models (by paper-trail-gem)
Discard
🃏🗑 Soft deletes for ActiveRecord done right (by jhawthorn)
Our great sponsors
| PaperTrail | Discard | |
|---|---|---|
| 18 | 5 | |
| 6,693 | 2,015 | |
| 0.4% | - | |
| 5.9 | 6.0 | |
| 3 months ago | 3 months ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PaperTrail
Posts with mentions or reviews of PaperTrail.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-09.
-
Best rails tools to automatically handle logging of things like all a user's actions, or changes to a record in a module - primarily for audit purposes.
Start with https://github.com/paper-trail-gem/paper_trail
-
is there a gem for tracking adhoc rails console changes
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.
-
Adding soft delete to a Phoenix Commanded (CQRS) API
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.
- Looking for a Rails Gem that Audits Manual Database Changes
-
Temporality/time-travelling in DB with ActiveRecord?
Maybe you are looking for the papertrail gem? https://github.com/paper-trail-gem/paper_trail
- Looking for an observer gem
-
`method_missing': undefined method `has_paper_trail'
has_paper_trail is from the paper-trail-gem, do you have that installed?
-
What's your process to run ruby scripts on production?
If talking about console access on production: First this is pretty limited. Then, we have logic in place, that sets the public key, the person authenticated with to access the console as the whodunnit ID in paper-trail, so that at least all their changes are audited. The thing @bluehavana posted, with auditing everything that was entered in the console is a good idea as well.
-
PaperTrail VS time-travel - a user suggested alternative
2 projects | 18 Sep 2021
Discard
Posts with mentions or reviews of Discard.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-12.
- Accessing point in time data when data changes over time
-
What are the gems that every Ruby dev should know how to use?
discard - a soft-delete implementation that avoids a lot of the gotchas associated with paranoia or acts_as_paranoid gem.
-
Rails application boilerplate for fast MVP development
add discard
What are some alternatives?
When comparing PaperTrail and Discard you can also consider the following projects:
Audited - Audited (formerly acts_as_audited) is an ORM extension that logs all changes to your Rails models.
Paranoia - acts_as_paranoid for Rails 5, 6 and 7
Logidze - Database changes log for Rails
mongoid-history - Multi-user non-linear history tracking, auditing, undo, redo for mongoid.
ActsAsParanoid - ActiveRecord plugin allowing you to hide and restore records without actually deleting them.
ActiveRecord Import - A library for bulk insertion of data into your database using ActiveRecord.
Espinita - Audit activerecord models like a boss (and works with rails 4!)
arel-helpers - Useful tools to help construct database queries with ActiveRecord and Arel.
ActiveRecordExtended - Adds additional postgres functionality to an ActiveRecord / Rails application
Destroyed At - ActiveRecord Mixin for Safe Destroys
PaperTrail vs Audited
PaperTrail vs Paranoia
PaperTrail vs Logidze
Discard vs Paranoia
PaperTrail vs mongoid-history
PaperTrail vs ActsAsParanoid
PaperTrail vs ActiveRecord Import
PaperTrail vs Espinita
Discard vs ActsAsParanoid
Discard vs arel-helpers
Discard vs ActiveRecordExtended
Discard vs Destroyed At