Like cgit, but in rust. Forked from rgit.
  • Rust 87.2%
  • HTML 8.9%
  • SCSS 3.6%
  • Dockerfile 0.2%
  • Makefile 0.1%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-08-18 08:21:16 -05:00
.cargo Expose tokio-console 2024-05-12 11:03:58 +01:00
docs/screenshots docs: Add screenshots 2026-05-08 08:06:51 -05:00
src syntax: Ensure sources without a highlighter start at line 1 2026-08-18 08:18:21 -05:00
statics tags: Render commit tags inline with commit messages 2026-05-07 13:52:45 -05:00
templates templates: Ensure diff_stats block XSS attempts 2026-07-14 20:46:41 -05:00
themes Move from syntect to tree-sitter 2024-09-29 04:07:03 +04:00
tree-sitter-grammar-repository version: Bump dependencies; version to 0.3.1 2026-07-14 21:00:42 -05:00
.dockerignore dockerignore updates 2026-04-13 18:00:45 -07:00
.gitignore Add flake.nix 2022-12-04 20:29:29 +00:00
build.rs rebrand/cleanup: Forking under a new name. gitore 2025-11-21 16:13:14 -06:00
Cargo.lock version: bump to 0.3.2 (as well as bump dependencies) 2026-08-18 08:21:16 -05:00
Cargo.toml version: bump to 0.3.2 (as well as bump dependencies) 2026-08-18 08:21:16 -05:00
deny.toml Update dependencies 2025-04-08 02:13:37 +07:00
docker-compose.yml Fix bind address in docker-compose.yml 2026-04-12 14:59:49 -07:00
Dockerfile Include Git in Dockerfile 2026-04-13 18:00:06 -07:00
gitore.png README: reduce logo size 2025-11-21 16:17:57 -06:00
LICENSE license: Relicense to MIT from WTFPL 2025-11-25 12:47:39 -06:00
Makefile version: Bump to 0.2.1 2025-12-12 14:01:07 -06:00
README.md README: Minor updates 2026-05-08 08:25:45 -05:00
rustfmt.toml Split repo methods into their own modules 2022-07-23 14:14:56 +01:00
taplo.toml Move to crane 2024-09-28 15:00:37 +04:00

gitore

gitore

Introduction

A gitweb/cgit-like interface for the modern age. Written in Rust using Axum, gitoxide, Askama and RocksDB.

Includes a dark mode for late night committing.

✨Screenshots

Table of Contents

Features

  • Efficient Metadata Storage
    RocksDB is used to store all metadata about a repository, including commits, branches, and tags. Metadata is reindexed, and the reindex interval is configurable (default: every 5 minutes), resulting in up to 97% faster load times for large repositories.

  • On-Demand Loading
    Files, trees, and diffs are loaded using gitoxide directly upon request. A small in-memory cache is included for rendered READMEs and diffs, enhancing performance.

  • Dark Mode Support
    Enjoy a dark mode for late-night committing, providing a visually comfortable experience during extended coding sessions.

Getting Started

Before you begin, ensure that you have the Rust toolchain and Cargo installed. If you haven't installed them yet, you can do so by following the instructions provided on the official Rust website:

Once you have Rust and Cargo installed, you can proceed with setting up and running the project.

Note: This software is designed to work exclusively with bare Git repositories. Make sure to set up bare repositories beforehand by following the Git on the Server documentation.

Usage

To get up and running quickly, run gitore with the following:

gitore -s /path/to/my-bare-repos -d /tmp/gitore-cache.db

Notes:

  • Repository indexing is recursive.
  • The database is quick to generate on smaller repositories, so this can be pointed to temporary storage.
  • An indexer status API is available at /api/scan-status

Configuration

Repository Description

To set a repository description, edit the file named description inside the bare git repository. Add your desired description text to this file.

Repository Owner

To assign an owner to a repository, edit the file named config inside the bare git repository and include the following content:

[gitweb]
    owner = "Al Gorithm"

Replace Al Gorithm with the desired owner's name.

Deployment

If you are putting gitore on the open internet, it is strongly recommended to put Anubis in front of it. While gitore can sustain a huge amount of rapid requests when compared to cgit, AI crawlers will quickly eat up large amounts of bandwidth from you.

Docker

Running gitore in Docker is straightforward. Follow these steps, ensuring that your repository directory is correctly mounted:

docker run --mount type=bind,source=/path/to/my-bare-repos,target=/git \
  --user $UID:$GID \
  -e SCAN_PATH=/git -e DB_STORE=/tmp/repo.db \
  -it codeberg.org/kallisti5/gitore:latest

Note: Replace $UID and $GID with the UID and GID of the user that owns the directory containing your repositories. If these values are incorrect, errors will occur. Learn how to find the UID of a user here.

Contributing

Pull requests are welcome

License

  • gitore is licensed under the MIT.
  • gitore is originally based on rgit, released under the WTFPL
    • Per the terms of the WTFPL license, gitore was relicensed under the more well known MIT.

Troubleshooting

Cloning Repositories

Repository not exported

Symptom: When attempting to clone repositories via HTTPS, you encounter the error message:

Git returned an error: Repository not exported

Solution: Create a file named git-daemon-export-ok in the bare git repository. This file signals to the git daemon that the repository is exportable.

Launching the Application

...is not owned by the current user

Symptom: When launching the application, you receive the error message:

repository path '/git/path/to/my/repository.git/' is not owned by the current user

Solution: Ensure that the user launching gitore or the Docker container has the same permissions as the user that owns the repositories directory.

Application Usage

Newly initialized repositories do not appear

Symptom: When using the application, a newly initialized bare repository without commits does not appear in the list.

Solution: Run the following command inside the repository to initialize it:

git pack-refs --all

Alternatively, push a commit with at least one file to the repository. This will also make the repository appear in the list.