Skip to content

Present #2

@pauljeanquart

Description

@pauljeanquart

KaB lab + GitWiki = KBitWiki

  • What if:

    • Development Wikis are on Github (Enterprise)
    • Source of Wiki is down
    • Network is down
  • Wiki

  • Fits in Pocket

  • Runs 24-48hrs + on singe charge

  • Hosts 100+ clients

Demo

Learned

  • Crawling 1000+ Repositories for their Wikis takes about an hour
    • Yields about 200 Wikis
      • About 1/3 are actually empty, who knows how many are stale
  • Wikis may redirect to README and other Markdown in the parent repo, may need additional means to fetch
  • Asset and Image urls need to be re-written to function
  • Some asset and image URLs are not in the Wiki Repository, alternate ways to fetch will be needed

Summary

  • Simple scripts and existing tools get you 80%
  • Wikis on SharePoint or other servers may be harder than GitHub
  • Small efforts to review and have minimum standards on Wikis would go miles

Future

  • A dynamic prioritized Runbook. Thx SC
  • Tracking of Tasks completed (and by whom). Thx SS
  • Potential external gateway via hotspot access (ie. cell data)
  • A Jabber like discussion board to help with communications
    • ;) not that the group text was bad
  • Could use SQLite and dotnet

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions