Project
Reverse Dependencies for puma
The projects listed here declare puma as a runtime or development dependency
0.05
Add drag and drop reordering to ActiveAdmin tables.
2020
2021
2022
2023
2024
2025
0.05
Standalone rack app to manage files onbehalf of your app
2020
2021
2022
2023
2024
2025
0.05
A command line utility to be run in Book repositories to stitch together their constituent Markdown repos into a temporary static-HTML-serving application
2020
2021
2022
2023
2024
2025
0.05
AJAX/Rails engine file browser for cloud storage services
2020
2021
2022
2023
2024
2025
0.05
integrated library system
2020
2021
2022
2023
2024
2025
0.05
Restart puma when files change
2020
2021
2022
2023
2024
2025
0.05
Universal knife verbs that work with your Chef repository
2020
2021
2022
2023
2024
2025
0.05
Start a markdown server in any directory
2020
2021
2022
2023
2024
2025
0.05
User interface for manage settings with rails-settings gem
2020
2021
2022
2023
2024
2025
0.05
Rack-mountable app to use and configure feature flags via the rollout gem
2020
2021
2022
2023
2024
2025
0.05
Use render in your Rails controllers and handle the response with Turbolinks.
2020
2021
2022
2023
2024
2025
0.04
A AlchemyCMS and Solidus integration
2020
2021
2022
2023
2024
2025
0.04
I am altria.
2020
2021
2022
2023
2024
2025
0.04
Makes Rails real time through websockets as a gem in the backend and as an Angular library in the front end.
2020
2021
2022
2023
2024
2025
0.04
This gem providers a small server to allow linking to arbitrarily-sized placeholder images.
2020
2021
2022
2023
2024
2025
0.04
Offload the rendering of slow view partials with ActiveJob and ActionCable to reduce page load times.
2020
2021
2022
2023
2024
2025
0.04
Beat Heroku's 60s boot timeout with a forward proxy.
2020
2021
2022
2023
2024
2025
0.04
The new de-facto for API testing your Rails application
2020
2021
2022
2023
2024
2025
0.04
I am Magi.
2020
2021
2022
2023
2024
2025
0.04
In version 5.0 the authors of the popular Ruby web server Puma chose to remove the
daemonization support from Puma, because the code wasn't wall maintained,
and because other and better options exist for production deployments. For example
systemd, Docker/Kubernetes, Heroku, etc.
Having said ...
2020
2021
2022
2023
2024
2025