BETAmodules.com is in beta — open to partnerships & joint ventures.Build with us
modules.com
⌘K

backend-toolkit

v0.0.1RubyGems· Ruby

backend-toolkit =============== A set of classes that simplify building a scalable backend for your app. Requirements ---------------- * redis (server and ruby gem) * json gem Installation ---------------- $ gem install backend-toolkit Development & Testing ---------------- $ bundle install $ rake Usage ---------------- ```ruby require 'backend-toolkit' # TO DO ``` Contributions ---------------- * Check commits history and issue tracker to be sure that no one else is working on the feature you want or are fixing the bug you found. * Fork the project. * Create a feature/bugfix branch and work on it. * Please add all tests needed to have a reasonably coverage of the new feature or bug that you are fixing. * Rebase your branch and open a pull request. * Please don't mess with the Rakefile, version, or history. License, Authors & Contributors ------- Check LICENSE.txt and AUTHORS.txt

The verdict
Abandoned. Last published 12 years ago. No recent activity — look for a maintained alternative.
No recent activity — look for a maintained alternative.
Live from the RubyGems registry · derived rules, not AI
How it scores
MaintenanceAbandoned
PopularityNiche
SecurityClean
LicenseUnknown
DepsZero deps
Maintenance
Last published 12 years ago.
Popularity
9 downloads / week
Security
No known advisories for this version (OSV).
License
No license declared.
Dependencies
No runtime dependencies
Recent releases
  • 0.0.112 years ago
backend-toolkit — backend-toolkit =============== A set of classes that simplify building a scalable backend for your app. Requirements ---------------- * redis (server and ruby gem) * json gem Installation ---------------- $ gem install backend-toolkit Development & Testing ---------------- $ bundle install $ rake Usage ---------------- ```ruby require 'backend-toolkit' # TO DO ``` Contributions ---------------- * Check commits history and issue tracker to be sure that no one else is working on the feature you want or are fixing the bug you found. * Fork the project. * Create a feature/bugfix branch and work on it. * Please add all tests needed to have a reasonably coverage of the new feature or bug that you are fixing. * Rebase your branch and open a pull request. * Please don't mess with the Rakefile, version, or history. License, Authors & Contributors ------- Check LICENSE.txt and AUTHORS.txt (Ruby / RubyGems) · Modules