noticed
Scenic
Our great sponsors
noticed | Scenic | |
---|---|---|
9 | 8 | |
2,282 | 3,338 | |
- | 1.0% | |
9.4 | 4.1 | |
7 days ago | 15 days 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.
noticed
-
How to Build Your Own Rails Generator
These kinds of generators exist in the Noticed gemand within Rails itself via the various rails scaffold commands and even the rails new command, which is a Rails generator itself.
-
System Notifications with Noticed and CableReady in Rails
The Noticed gem makes developing notifications fantastically easy by providing a database-backed model and pluggable delivery methods for your Ruby on Rails application. It comes with built-in support for mailers, websockets, and a couple of other delivery methods.
- Slack notification when record is created in a db table.
-
Help with receiving email notifications - hint would be appreciated
I highly recommend the noticed gem for sending notifications. It supports a bunch of different delivery methods, including email, and it's really well documented.
-
GSoC 2022 CircuitVerse | Week 5 and 6 Report
Currently, CircuitVerse uses activity_notification gem for the Notifications but the gem is not maintained any more and the notification page is very lagging. So we decided to replace the gem and we found noticed gem by chris oliver of Gorails.
-
User notifications with Rails, Noticed, and Hotwire
Rails developers that need to add a notification system to their application often turn to Noticed. Noticed is a gem that makes it easy to add new, multi-channel notifications to Rails applications.
-
Are there built in Ruby-tools to help you code out and monitor CRM-like workflows (e.g. upon action X, event Y will trigger in 5 days, and event Z in 15 days, etc). Need something that a user can monitor on a console.
Have you looked at Caffinate or noticed ?
-
Rails application boilerplate for fast MVP development
noticed for notifications
-
Learning Ruby: Things I Like, Things I Miss from Python
> I think often the things that don’t exist are not there for good reasons... using Stripe’s api for example from a module is pretty trivial in my experience, it’s just HTTP and you don’t need to be super clever about it.
It's way more involved than inserting an auth token header into an HTTP request and calling some API endpoint.
For example, what about verifying webhooks? The official libraries for Stripe (Python, Ruby, Node, PHP, Go, JS, etc.) deal with this for you.
But with Elixir, you're on your own. This is very low level code to have to deal with and it's extremely important you get it right.
You're left having to parse Stripe's specification on this and then implement the code yourself in Elixir. It's so tricky and involved that the Dashbit company (the creator of Elixir and members of the core team work there) wrote a blog post on it at https://dashbit.co/blog/how-we-verify-webhooks.
But before a few months ago that blog post didn't exist. Also this isn't the only thing you'll have to do yourself when it comes to interacting with Stripe.
Then you'll have to do similar things for other payment providers all which are different in a lot of ways, but with Rails you have the combination of having official Ruby clients from those payment providers and even the Pay gem which lets you support payments from multiple providers. That could easily be a few months of dev time just for that abstraction alone if you had to go about that from scratch and your implementation wouldn't have any track record until you start using it and ironing out the bugs from real world experience.
> Again notifications doesn’t sound particularly difficult and I don’t see why I’d want to rely on some complex gem that does every option when I don’t need them
Don't take this the wrong way but this seems to be the mindset of almost everyone I chatted with when it comes to Elixir. When someone asks how to do something, the answer is it's trivial or easy to implement but there's never any examples posted on how to do it.
In my mind trivial or easy means I can sit down in maybe a few hours or a day and write a production ready solution, complete with tests and have it work exactly how I want without running into any major roadblocks.
I'd be curious to see how you would implement https://github.com/excid3/noticed or https://github.com/excid3/pay. Based on your responses of saying these things are easy I'm guessing you've written large apps with Phoenix where you've developed features like this in a production app? It would be fantastic if you could post some code examples or a blog post on how you went about this. Not just to answer my specific question but I'm sure the community would appreciate having concrete examples of how it's done. This way more folks would use the framework.
Scenic
-
Database Views & Rails Active Record: defining new Model classes out of views
To model our Deliverable class, we will need a view. We will use the popular scenic gem, which provides some useful generators for creating views with their respective migrations, and utilities to handle views versioning.
-
Materialised views for serious performance gains
+1 for scenic - https://github.com/scenic-views/scenic
-
Most performant way to build an analytics dashboard from a relational database backend that only stores numeric values, where the data the end-user sees is "categorized" into numeric brackets (e.g. 60-79 = Med, 80-100 = High, etc)
If the data doesn't need to be close to real-time, and if your DB can handle a bit of load, I'd use a "batch" approach. To do this, I'd create a materialized view in your relational DB that you'd then refresh periodically. The easiest way to do this is with the `scenic` gem. Once you've done this, you can simply create a new model and set the `table_name` to the name of the materialized view, and then treat it as a regular model.
- Utilizando views SQL no Ruby on Rails
-
Frameworks for SQL Development in Rails?
I use the scenic gem to manage views which uses raw sql files: https://github.com/scenic-views/scenic
-
Rails application boilerplate for fast MVP development
add scenic
-
Logidze 1.0, postgres-specific alternative to eg paper_trail for recording ActiveRecord change history
TIL about fx gem for storing triggers in schema.rb. That makes me so happy because scenic gem for creating database views is one of my favorites. Postgres is very powerful and it's great to see tools for exposing that through Rails.
What are some alternatives?
Sidekiq - Simple, efficient background processing for Ruby
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.
Ahoy - Simple, powerful, first-party analytics for Rails
PgHero - A performance dashboard for Postgres
heya - Heya 👋 is a campaign mailer for Rails. Think of it like ActionMailer, but for timed email sequences. It can also perform other actions like sending a text message.
SecondBase - Seamless second database integration for Rails.
web-push - Web Push library for Node.js
Polo - Polo travels through your database and creates sample snapshots so you can work with real world data in development.
Annotate - Annotate Rails classes with schema and routes info
SchemaPlus - SchemaPlus provides a collection of enhancements and extensions to ActiveRecord
unholy - a ruby-to-pyc compiler
Ruby PG Extras - Ruby PostgreSQL database performance insights. Locks, index usage, buffer cache hit ratios, vacuum stats and more.