A (static) git repository browser [mirror]
ac105c8383
When the number of commits on a branch page is less than 'commits_per_page', the pagination "next" link is disabled, indicating correctly that this is the final page. However, if the number of commits on the branch page is exactly 'commits_per_page', then the "next" link is incorrectly enabled, even on the final page. When clicked, the user is taken to a "404 Page not found" error page, which makes for a poor user experience. Fix this problem by reliably detecting when the branch page is the final one. Do so by asking for (but not displaying) one commit more than actually needed by the page. If the additional commit is successfully retrieved, then another page definitely follows this one. If not retrieved, then this is definitely the final page. (Unfortunately, the seemingly more expedient approach of checking if the final commit on the current page is a root commit -- has no parents -- is not a reliable indicator that this the final page since a branch may have multiple root commits due to merging.) Signed-off-by: Eric Sunshine <sunshine@sunshineco.com> Signed-off-by: Alberto Bertogli <albertito@blitiri.com.ar> |
||
---|---|---|
hooks | ||
static | ||
views | ||
.gitignore | ||
git-arr | ||
git.py | ||
LICENSE | ||
README | ||
sample.conf | ||
TODO | ||
utils.py |
git-arr - A git repository browser ---------------------------------- git-arr is a git repository browser that can generate static HTML instead of having to run dynamically. It is smaller, with less features and a different set of tradeoffs than other similar software, so if you're looking for a robust and featureful git browser, please look at gitweb or cgit instead. However, if you want to generate static HTML at the expense of features, then it's probably going to be useful. It's open source under the MIT licence, please see the LICENSE file for more information. Getting started --------------- You will need Python, and the bottle.py framework (the package is usually called python-bottle in most distributions). If pygments is available, it will be used for syntax highlighting, otherwise everything will work fine, just in black and white. First, create a configuration file for your repositories. You can start by copying sample.conf, which has the list of the available options. Then, to generate the output to "/var/www/git-arr/" directory, run: $ ./git-arr --config config.conf generate --output /var/www/git-arr/ That's it! The first time you generate, depending on the size of your repositories, it can take some time. Subsequent runs should take less time, as it is smart enough to only generate what has changed. You can also use git-arr dynamically, although it's not its intended mode of use, by running: $ ./git-arr --config config.conf serve That can be useful when making changes to the software itself. Contact ------- If you want to report bugs, send patches, or have any questions or comments, just let me know at albertito@blitiri.com.ar.