Project

Reverse Dependencies for rake

The projects listed here declare rake as a runtime or development dependency

0.0
No commit activity in last 3 years
No release in over 3 years
CLI for initializing a new modular Sinatra application with default configurations. The application is setup with a structure that is similar to Rails
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
Repository is archived
No commit activity in last 3 years
No release in over 3 years
Kata-like practice building a gem with Bundler, TDD, Travis CI & Coveralls.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
Repository is gone
No release in over 3 years
Usage: include sinesp_client_v2 and call SinespClientV2.search(plate: 'ABC1234')
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
No release in over 3 years
Sing will create the basic directory structure and base files for a Sinatra webapp. It creates your Gemfile (containing haml, sinatra, and rubygems), config.ru, index.haml, layout.haml (includes Twitter Bootstrap, and the current jQuery), application.css.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
No release in over 3 years
Account number to bank branch and bank code converter.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
No commit activity in last 3 years
No release in over 3 years
Calculators for Singapore Charitable Donations. Supports CDAC, ECF, MBMF, and SINDA.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
Repository is gone
No release in over 3 years
A Singapore's Central Provident Fund (CPF) contributions calculator.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
No commit activity in last 3 years
No release in over 3 years
Calculates for the employer contributions for the Skill Development Levy Act contribution per employee.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Unified system image creation using Packer
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Creates config files from ENV; Read/writes state from postgres database
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
Repository is gone
No release in over a year
Single dev
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
 Popularity
0.0
No commit activity in last 3 years
No release in over 3 years
Run a block of code only if a system level file lock can be obtained for a given filepath.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
Repository is archived
No commit activity in last 3 years
No release in over 3 years
A Ruby client library for accessing the SinglePlatform API.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
A simple way to get data from the Single Platform api.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Globalize3 successor which use only one table to store all the translations.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
It just makes sense to store mutable, site-wide, admin-level settings in the database. Right? A key-value table may be more flexible, but maybe we don't want to be flexible! If you truly want that flexibility: http://github.com/stephencelis/kvc
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Invoke instance methods through a singleton alias likeKlass.method(*args) instead of Klass.new(*args).method
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
No commit activity in last 3 years
No release in over 3 years
Evaluate block in the context of singleton class
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026