DatabaseValidations
Lograge
| DatabaseValidations | Lograge | |
|---|---|---|
| 3 | 7 | |
| 503 | 3,405 | |
| 0.6% | - | |
| 0.0 | 5.0 | |
| 11 months ago | about 2 months ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
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.
DatabaseValidations
-
Uniqueness validation does not work since the beginning of Ruby on Rails.
DatabaseValidations provides database-driven validations for ActiveRecord.
-
Ecto's uniqueness constraint vs. Rails' uniqueness validation
Love this post, great exploration of the nuances of uniqueness validations.
I came here to mention that there is also the https://github.com/toptal/database_validations gem which allows you to handle uniqueness validations in Rails in a similar manner to Ecto.
-
Rails application boilerplate for fast MVP development
add database_validations
Lograge
-
Manage Your Ruby Logs Like a Pro
You can choose from a number of third-party logging libraries, including Logging — based on Java's log4j library — and Lograge. Lograge is a feature-rich logging library meant to simplify the often messy and verbose Rails logs characteristic of the default application logger.
- 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.
-
What are your top useful gems?
Also a big fan of Lograge, because I just can't stand Rails default logs.
-
Rails application boilerplate for fast MVP development
add lograge
-
Searchable logs with Filebeat and Elastic Stack
To output rails logs into JSON format, we are using lograge gem once you add it in Gemfile and bundle install it will be available to use in you application.
-
Logging in Ruby with Logger and Lograge
There are plenty of options when it comes to picking up a 3rd-party logging framework. The most popular of these is Lograge. Let's take a look at it!
-
Just curious : why is Rails default logging so verbose ?
Check out https://github.com/roidrage/lograge for some settings that work nicely for us in production
What are some alternatives?
DatabaseConsistency - The tool to avoid various issues due to inconsistencies and inefficiencies between a database schema and application models.
Semantic Logger - Semantic Logger is a feature rich logging framework, and replacement for existing Ruby & Rails loggers.
SchemaPlus - SchemaPlus provides a collection of enhancements and extensions to ActiveRecord
Fluentd - Fluentd: Unified Logging Layer (project under CNCF)
BatchLoader - :zap: Powerful tool for avoiding N+1 DB or HTTP queries
LogStashLogger - Ruby logger that writes logstash events
Upsert - Upsert on MySQL, PostgreSQL, and SQLite3. Transparently creates functions (UDF) for MySQL and PostgreSQL; on SQLite3, uses INSERT OR IGNORE.
Log4r - Log4r is a comprehensive and flexible logging library for use in Ruby programs. It features a heirarchical logging system of any number of levels, custom level names, multiple output destinations per log event, custom formatting, and more.
Lol DBA - lol_dba is a small package of rake tasks that scan your application models and displays a list of columns that probably should be indexed. Also, it can generate .sql migration scripts.
Logging - A flexible logging library for use in Ruby programs based on the design of Java's log4j library.
SecondBase - Seamless second database integration for Rails.
Sidekiq - Simple, efficient background processing for Ruby