Project

Reverse Dependencies for enola-guides

The projects listed here declare enola-guides as a runtime or development dependency

0.0
The project is in a healthy, maintained state
Fail the build when a change breaks your Rails app's architecture: a model that starts calling a controller, a job that renders, a new dependency cycle. Only what the change introduced is graded, never what the app already carries. Adds the Rails layer to the enola gem: `rails generate enola:install` writes enola/constraints/ from the enola-guides starter laws and binds the recipes the released enola's own `constraints init` picks for the app, and the enola:init, enola:snapshot and enola:check rake tasks drive the binary the `enola` gem fetches and verifies. Pure Ruby; no binary, nothing compiled.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
0.0
The project is in a healthy, maintained state
The binary this gem fetches is not an enola-labs release. It is a build cut from https://github.com/misabegovic/enola, a fork of enola, whose release notes name what differs from upstream release by release; this gem drives channel release 0.4.32.1, built on enola 0.4.32. Everything else is the enola gem's wrapper, unchanged: fetched on first use, verified against the checksums the release publishes, cached per user, every command and exit code forwarded. Use the enola gem to run stock upstream instead. What the fork adds: `munola init` writes the recipe catalogue the enola-guides gem carries (Ember, data ownership, API boundaries, background work, a tenant foreign key) into the project, binds the recipes its tree justifies, and turns both Ruby providers on by default. Under Rails it adds `rails generate munola:install`; the enola:* rake tasks come from enola-rb and drive munola's binary. Offered upstream where it fits; no binary here, nothing compiled.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026