

Stagit
2 likes
Stagit is a static page generator for git, and is focused on a minimalist design and approach.
Features
Properties
- Minimalistic
Features
Git Support
- Static Site Generator
Stagit News & Activities
Highlights All activities
Recent activities
POX added Stagit as alternative to Static CMS and Glyph static site generator- POX updated Stagit
- POX removed all alternatives from Stagit
Stagit information
No comments or reviews, maybe you want to be first?
Post comment/reviewWhat is Stagit?
Stagit is a static page generator for git, and is focused on a minimalist design and approach.
Features
- Log of all commits from HEAD.
- Log and diffstat per commit.
- Show file tree with linkable line numbers.
- Show references: local branches and tags.
- Detect README and LICENSE file from HEAD and link it as a webpage.
- Detect submodules (.gitmodules file) from HEAD and link it as a webpage.
- Atom feed of the commit log (atom.xml).
- Atom feed of the tags/refs (tags.xml).
- Make index page for multiple repositories with stagit-index.
- After generating the pages (relatively slow) serving the files is very fast, simple and requires little resources (because the content is static), only a HTTP file server is required.
- Security: all pages are static. No CGI or dynamic code is run for the interface. Using it with a secure httpd such as OpenBSD httpd it is privilege-separated, chroot(2)'d and pledge(2)'d.
- Simple to setup: the content generation is clearly separated from serving it. This makes configuration as simple as copying a few directories and scripts.
- Usable with text-browsers such as dillo, links, lynx and w3m.
Cons
- Not suitable for large repositories (2000+ commits), because diffstats are an expensive operation, the cache (-c flag) or (-l maxlimit) is a workaround for this in some cases.
- Not suitable for large repositories with many files, because all files are written for each execution of stagit. This is because stagit shows the lines of textfiles and there is no "cache" for file metadata (this would add more complexity to the code).
- Not suitable for repositories with many branches, a quite linear history is assumed (from HEAD).





