> ## Documentation Index
> Fetch the complete documentation index at: https://www.towbar.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# GlitchTip

> GlitchTip helps teams track application errors, performance, and uptime.

export const UseCaseNavigation = () => {
  useLayoutEffect(() => {
    const storageKey = "towbar-use-case-open-groups";
    const groupSelector = "#sidebar li[data-title] > button[aria-expanded]";
    let restoring = false;
    let frame = 0;
    function storedGroups() {
      try {
        return new Set(JSON.parse(sessionStorage.getItem(storageKey) || "[]"));
      } catch {
        return new Set();
      }
    }
    function save(groups) {
      try {
        sessionStorage.setItem(storageKey, JSON.stringify([...groups]));
      } catch {}
    }
    function groupName(button) {
      return button.parentElement?.dataset.title;
    }
    function rememberOpenGroups() {
      const groups = new Set();
      for (const button of document.querySelectorAll(groupSelector)) {
        if (button.getAttribute("aria-expanded") === "true") {
          const name = groupName(button);
          if (name) groups.add(name);
        }
      }
      save(groups);
    }
    function restoreOpenGroups() {
      frame = 0;
      const groups = storedGroups();
      if (!groups.size) return;
      restoring = true;
      for (const button of document.querySelectorAll(groupSelector)) {
        if (groups.has(groupName(button)) && button.getAttribute("aria-expanded") === "false") {
          button.click();
        }
      }
      restoring = false;
    }
    function scheduleRestore() {
      if (!frame) frame = requestAnimationFrame(restoreOpenGroups);
    }
    function onClick(event) {
      if (restoring || !(event.target instanceof Element)) return;
      const button = event.target.closest(groupSelector);
      if (button) {
        const name = groupName(button);
        if (!name) return;
        const groups = storedGroups();
        if (button.getAttribute("aria-expanded") === "true") groups.delete(name); else groups.add(name);
        save(groups);
        return;
      }
      if (event.target.closest('a[href^="/docs/use-cases/"]')) {
        rememberOpenGroups();
      }
    }
    const observer = new MutationObserver(scheduleRestore);
    document.addEventListener("click", onClick, true);
    observer.observe(document.getElementById("sidebar") || document.body, {
      childList: true,
      subtree: true
    });
    scheduleRestore();
    return () => {
      document.removeEventListener("click", onClick, true);
      observer.disconnect();
      cancelAnimationFrame(frame);
    };
  }, []);
  return null;
};

<UseCaseNavigation />

**Upstream source:** [Current installation guide](https://glitchtip.com/documentation/install/).

GlitchTip 6 can run its web and background work in one container with PostgreSQL. Valkey is optional for a small instance; `SERVER_ROLE=all_in_one` and an empty `VALKEY_URL` select that path. The uploads volume keeps attachments.

## Towbar manifests

<CodeGroup>
  ```yaml title=".towbar/datastores/glitchtip-postgres.datastore.yml" theme={"system"}
  id: glitchtip-postgres
  name: GlitchTip PostgreSQL
  type: postgres
  container:
    network: application
    networkAlias: glitchtip-postgres
    resources:
      cpus: 1
      memory: 1g
  secrets:
    runtime:
      - POSTGRES_USER
      - POSTGRES_DB
      - POSTGRES_PASSWORD
  environments:
    production:
      server: 192.0.2.10
  ```

  ```yaml title=".towbar/services/glitchtip.service.yml" theme={"system"}
  id: glitchtip
  name: GlitchTip
  buildServer: null
  deployment:
    type: image
    image: glitchtip/glitchtip:6
  container:
    port: 8000
    network: application
    volumes:
      - name: uploads
        mountPath: /code/uploads
        initialData: image
  environments:
    production:
      server: 192.0.2.10
  rollout:
    type: recreate
    maintenanceMode: true
    reason: Persistent application data uses a single writer
  secrets:
    runtime:
      - DATABASE_URL
      - SECRET_KEY
      - GLITCHTIP_DOMAIN
      - ALLOWED_HOSTS
      - CSRF_TRUSTED_ORIGINS
      - SERVER_ROLE
      - VALKEY_URL
      - EMAIL_URL
  domains:
    primary: glitchtip.example.com
  tls:
    mode: direct
  ```
</CodeGroup>

## Configure

1. Prepare the example server, connect the repository, and map `production` to the branch containing these manifests. Replace the example server IP and domain. Commit the manifests, then sync the repository and inspect the resolved configuration.
2. Save the initialization values in the table below for the postgres Datastore under **Datastore → Settings → Secrets**. Deploy it first and wait for readiness. These values create the database and user only on an empty volume.
3. Set the Service's declared runtime values under **Service → Settings → Secrets** using the table below. Replace descriptions and placeholders with actual values; do not commit passwords or keys.
4. Keep the Service's named volumes attached across deployments. Towbar's Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
5. Deploy the Service, then perform the checks below before enabling auto-deploy.

## Datastore values

Save these in each Datastore's **Settings → Secrets** before deploying it. Use the suggested names or choose your own, then use the same names and passwords in the Service connection values below.

| Datastore          | Key                 | Suggested value                                                                           |
| ------------------ | ------------------- | ----------------------------------------------------------------------------------------- |
| GlitchTip postgres | `POSTGRES_DB`       | glitchtip                                                                                 |
| GlitchTip postgres | `POSTGRES_USER`     | glitchtip                                                                                 |
| GlitchTip postgres | `POSTGRES_PASSWORD` | Run `openssl rand -hex 32`; save its output and reuse it in the Service connection value. |

## Runtime values

Save these values on the Service after the repository sync. The manifest declares required keys, not their values.

| Key                    | Value to save                                                                                                   |
| ---------------------- | --------------------------------------------------------------------------------------------------------------- |
| `DATABASE_URL`         | `postgres://glitchtip:PASSWORD@glitchtip-postgres:5432/glitchtip` (replace `PASSWORD` with `POSTGRES_PASSWORD`) |
| `SECRET_KEY`           | Generate with `openssl rand -hex 32`.                                                                           |
| `GLITCHTIP_DOMAIN`     | [https://glitchtip.example.com](https://glitchtip.example.com)                                                  |
| `ALLOWED_HOSTS`        | glitchtip.example.com                                                                                           |
| `CSRF_TRUSTED_ORIGINS` | [https://glitchtip.example.com](https://glitchtip.example.com)                                                  |
| `SERVER_ROLE`          | all\_in\_one                                                                                                    |
| `VALKEY_URL`           | Leave empty for the small PostgreSQL-backed setup.                                                              |
| `EMAIL_URL`            | Your SMTP URL, or `consolemail://` for a test that does not send email.                                         |

## Verify

Create a project, send a test event, and verify it appears. Configure real SMTP before relying on invitations or email alerts; back up PostgreSQL and uploads.

For field constraints, see [Service manifest](/docs/services/manifest) and [Datastore manifest](/docs/datastores/manifest).