Project

Reverse Dependencies for rails

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

0.0
No release in over 3 years
Don't send mail in sandbox console.
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
Repository is archived
No release in over 3 years
Low commit activity in last 3 years
Sandboxy allows you to use virtualdata-oriented environments inside a Railsapplication while being able to switch inbetween at runtime. It achieves that by using acombination of Rack Middleware and ActiveRecord.
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
ActiveConfiguration is an engine that exposes a generic settings store to ActiveRecord models. Made for very configurable applications, it allows you to avoid implementing specific ways to store settings for each model that needs such configuration. If your application isn't very configurable, ActiveConfiguration is probably overkill.
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 release in over 3 years
Sanity Check For Environment's processes
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
sap_anywhere的接口封装.
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
Sape.ru links exchange system integration
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
This is a simple file manager created in RoR as a mountable engine. It's created for Railsyard CMS but will also work without it. To use it in RY use ry-filemanager gem.
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
There's a lot of open issues
Hasslefree autoconfiguration for logging, metrics and exception collection.
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
Sapling lets you seed your new features to just a few users at a time. You can change which and how many users are seeded for a feature dynamically by updating the database via the Sapling API. Core features are the ability to seed a feature for specific users and/or a percentage of users.
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 release in over 3 years
Essential models, mailers, and classes for the Sapna gale test e-commerce project.
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
Repository is gone
No release in over 3 years
RabbitMQ based replacement for PaperTrail
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
Repository is gone
No release in over 3 years
SASS version of the CSS toolkit from Twitter for Rails 3.1+ asset pipeline.
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
Repository is gone
No release in over 3 years
Satchel - a mountable Rails engine for activity streams
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
SATySFi template for 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 gone
No release in over 3 years
Rails' default update_attributes behavior is that when any validation fails, none of the data gets saved. However, in some instances this is not the most ideal behavior. If you import partial data which users then have the task of completing, not saving partially completed forms can create a really negative user experience and decrease overall completion (or conversion) rates. This gem encapsulates the logic I've used to ensure that partially completed forms still persist.
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
I saw user clicking on that button there.
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
ETags for ActiveFedora datastreams.
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
ETags for ActiveFedora datastreams.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026