Rails engine that can plug/unplug features with notice

pokeplot is a tool to collect collect pokemon go spawning data and store it in mongodb

Cloud storage to image gallery + image proxy + file api

Monitor process memory and CPU over time

Most Rails blogging tools include everything you could ever want, including things you don't. Proclaim tries to provide the simplest (yet beautiful) implementation of a blog via a mountable engine; if more functionality is desired, it can easily be combined with other engines.

The missed parts of prometheus/client_ruby

Application to gather prometheus style metrics # Usage Install the gem into your gemfile ```gem prometheus-collector``` Install your gemset ```bundle install``` Consume the program. ``` require 'prometheus/collector' class Guage < Prometheus::Collector::Extensions::Base install def run # Do some things that would be collected in Prometheus::Client Objects end end ``` Mount the Prometheus::Collector::Application application, or start it from your app.rb ``` Prometheus::Collector::Application.start ``` # How it works The collector app makes use of the Prometheus client collector and exporter middleware to allow you to write custom applications that export prometheus style metrics. It is designed as a bare-bones scaffold to get you off the ground with a ruby applet to get some statistics. It utilizes rack and its middleware. The interface is fairly straightforward: Your Metric Executing code needs to extend Prometheus::Collector::Extensions::Base for 'repeatedly-runbable' operations and Prometheus::Collector::Extensions::Once for something that should only be executed Once. Your class should implement an instance level `run` function, and may optionally implement a class level `schedule` function: This must return a `cron` style string to tell the application when to invoke your `run` code. By default, `schedule` is set to `* * * * *` which would allow the code to be executed every minute. ### Scheduling Scheduling is implemented via em-cron. Thus the re-scheduling of a task should occur within the parameters of the `schedule` string but is evaluated upon completion. Thus in normal operation, the code should not execute more than one `run` of a given worker definition at a time.

Visualize results of pry commands to a website.

Base configuration for Publishing Platform applications

Test configuration and dependencies for applications on Publishing Platform

A Puma webserver plugin for automatic access to certificates from Let's Encrypt and any other ACME-based CA.

Periodically check Puma backlog and write a flag file

Rails-on-Puma? Clock your 'rails server' command!

Puma plugin to restart Puma automatically when a file gets modified.

Puma plugin to fix running too many fsevent_watch processes

Puma plugin to log server stats whenever the number of concurrent requests exceeds a configured threshold.

Collect Puma stats and send them to NewRelic via control app

Send puma metrics to Dogstatsd via a background thread

NOTE: This is a fork of puma-plugin-telemetry, modified to: - Support Puma 7 - Add LogTarget, with custom formatter: and transform: options - Warn about socket telemetry on unsupported platforms Puma plugin which should be able to handle all your metric needs regarding your webserver: - ability to publish basic puma statistics (like queue backlog) to both logs and datadog - ability to add custom target whenever you need it - ability to monitor puma socket listen queue (!) - ability to report requests queue time via custom rack middleware - the time request spent between being accepted by Load Balancer and start of its processing by Puma worker

Add pool usage statistics within your log files.