4 ms·
We setup multiple[1] Gollum wikis at work, and had the following changes: - Removed a bunch of features that were confusing to our non-dev users - Used nginx/
by josegonzalez 12y ago
We setup multiple[1] Gollum wikis at work, and had the following changes:
- Removed a bunch of features that were confusing to our non-dev users
- Used nginx/lua to do custom OAuth-based authentication [2]
- Set the committer's name and email to the currently authenticated user (from an env var in the request)
- Mucked around with the templates
- Added a /_status endpoint to do simple healthchecks for our load-balancer
- Extended `process_page_link_tag` to make it a bit more flexible when constructing links
- Added hipchat notifications for when pages are updated
Would be nice to see a system that allowed us to do the above, as we're not really all that in love with Gollum. The git part was great for our initial migration, not so great for wiki fault-tolerance...
[1] One for employees, one for freelancers, etc.
[2] Blog post on oauth with nginx/lua here: http://chairnerd.seatgeek.com/oauth-support-for-nginx-with-lua/ http://chairnerd.seatgeek.com/oauth-support-for-nginx-with-l...
- scragg 12y agoI was thinking about forking gollum but I'm a ruby newb. I thought about leaving auth out but I think it might be useful to many people. I want the user to be able to disable it and use some kind of signed cookie based auth. I like the Nginx OAuth method, I will check it out, thanks.