Opened 2 years ago
Closed 2 years ago
#65 closed Service Improvement (Works For Me)
Migrate documentation away from trac/wiki to markdown hosted on git repositories.
| Reported by: | D Delmar Davis | Owned by: | D Delmar Davis |
|---|---|---|---|
| Priority: | Important | Milestone: | Make Shit Happen / Own Your Shit. |
| Component: | Development | Keywords: | git trac markdown mkdocs |
| Cc: | Joe Dumoulin |
Description
I have been moving towards bundling documentation, script, and configuration files into git repositories and using the markdown to create static web sites. (Also using this to flesh out digithink.com which has traditionally been sysadmin oriented). See www.digithink.com which is generated from https://github.com/feurig/digithink. Note that buildnotes that were from other repositories are included as git submodules (win/win).
Documentation for creating the documentation is at http://www.digithink.com/buildnotes/mkdocs-server-configuration/mkdocs-server-configuration/
I will probably scrub the wiki docs once I have the timestamps added to the markdown files. At that point systems documentation will live there.
Or as that little punk at flight stats said about devops "It's all code". So fuck it. may as well treat it that way.
Change History (2)
comment:2 Changed 2 years ago by
| Resolution: | → Works For Me |
|---|---|
| Status: | assigned → closed |
RedirectMatch /serverdocs/wiki/(.*) http://www.digithink.com/serverdocs/$1/
May tweek this a bit but for the most part the old documentation redirects to the new documentation.
I am going to close this out. Cause it works for me.
Should also look at forwarding any links using mod_rewrite.
https://serverdocs.suspectdevices.com/serverdocs/wiki/MyWikiPage