Skip to content
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.

Fixed generators to work from a mountable Rails engine #130

Closed
wants to merge 0 commits into from

Conversation

joelvh
Copy link
Contributor

@joelvh joelvh commented Sep 26, 2015

Added Rails engine "namespace" to asset paths when installing CASino. Added migrations generator to copy migrations because the built-in rake railties:install:migrations does not work when running the command on a Rails engine. It's a simple fix to copy the files.

Given, we may have a special case where we're mounting CASino in another mountable Rails engine.

@pencil
Copy link
Member

pencil commented Oct 1, 2015

Thanks for your PR. How can I reproduce the problem you are facing with the current implementation? Does this change the behavior of the most comment use case? Do we have to migrate existing installations?

@joelvh
Copy link
Contributor Author

joelvh commented Oct 7, 2015

@pencil you can test this by creating a mountable Rails engine, and mounting CASino. Then (from the rails engine root) try running the generator rails g casino:install or the Rake command rake casino:install:migrations. It doesn't seem to work (with the old code), but works now with this new generator.

@pencil
Copy link
Member

pencil commented Nov 4, 2015

Does this change anything for existing installations? Are the commands still the same?

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.201% when pulling fed0626 on identification-io:master into fed0626 on rbCAS:master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants