# Back > An extremely simple git issue tracking system. Inspired by tvix's panettone. ## Usage `back` is modelled after `cgit`, only for `git-bug` initialized repositories. The server is than started at `http://127.0.0.1:8000` and provides access to the issues (bugs) tracked via `git-bug`, via multiple routes: ### `/` The default index is a list of all repositories that have `git-bug` data in them. ### `/issues/` This path displays all issues in `` (i.e., open or closed) for the repository at ``. ### `/issue/` Displays the actual issue with `id` ``. Beware, that the `` is sourced from the actual git object associated with the issue create commit. As such, it is not the same ID, as displayed by the `git-bug` CLI. ### `/issues/feed` An RSS feed usable to subscribe to. This includes all issues and all comments of issues. ## Configuration file The config file is passed to `back` via the first command line argument. It is written in JSON. An example configuration file is available at [`./contrib/config.json`](./contrib/config.json). Following keys are required: ### `source_code_repository_url` The URL to the source code of this instance of `back`. ### `root_url` The root URL this instance of `back` is hosted at. For example: `https://issues.foss-syndicate.org`. This is required by the RSS feed to generate links to the various issues/comments. ### `scan_path` The path under which to search for the repositories as specified by the `projects.list` file. This is semantically the same as `cgit`'s `scan-path`. ### `project_list` The path to the file specifying the repositories to search. A repository path per line. This is semantically the same as `cgit`'s `project-list`. ### Note `back` needs write access to the repository, because of internal `gix` and `git` object reasons. ## Licensing This project complies with the REUSE v3.3 specification. This means that every file clearly states its copyright.