Make publishable as a gem. #80 #84
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@danielfarrell : I had published my previous version to rubygems.org. Want me to do so with this one as well, or do you want your name attached to it there? |
|
And apologies for doing this pull request off of master. Want me to move it to a branch and re-do? |
|
We'll probably do this, but it will end up being in it's own repo. I'll close one it's done. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add the necessary files to make publishable as a gem. This is maybe a little kludgy and I don't know if tehre's a better way to do it: because the original fork has the files laid out differently than rails gems, need, in the .gemspec file I create the needed folders and copy the js & css to them. There's no way to clean that up, though, but I have added those to the .gitignore. Fixes #80.