-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to use a per repository config file #15
Comments
Can you explain what kind of customization you'd want to do with this? |
I'm just thinking of a plain ruby file where one could pull in additional dependencies, add routes/templates etc. to the sintra instance. Looking at http://github.com/github/gollum/issues/#issue/13 - I think over time people will want little bits of extra functionality added here and there, and I'm not aware of a way to currently do that without maintaining your own fork (or bloating the core). Perhaps overtime additional functional could be incorporated into a Gollum::More type package. |
Agreed. The ability to extend Jekyll made it incredibly useful—I was finally able to drop my fork and stick with the core. Some type of system that would allow basic customizations, like ToC generators or listings of all the files in the repo (like the MediaWiki enhancements listed in issue 13 above) would be fantastic. |
Would something like this work:
Patch Ahead:
|
Fixed! |
New implementation of ls_tree. Fixes #15.
It would make it a bit easier to extend Gollum without having to mess with core. I'm thinking along the lines of a
app.rb
orconfig.rb
file that gets added to the repo that will be read by Gollum when using the web-interface.The text was updated successfully, but these errors were encountered: