and
What like about ikiwiki is that instead of always running as daemon, it's launched via a git post-update hook. After regenerating static html for the content you've changed it's done. It does support editing content via a web interface, but all that needs is CGI. The downside is that you need a thorough understanding of unix permissions to make it work.
- 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-l...
What are those? Gollum is a wiki[1], yes? Ghost is the new blogging platform[2]? What's Dillinger?
I really like the idea of this wiki as well as the look of it. I could definitely see myself using this in the future. I had spent some time a couple months ago looking into what Flask-based wikis were available but my results turned up very little. I'll definitely be watching this repo as it grows.
I'm loading up with Vagrant right now. Any thoughts on dockerizing it?
