Christoph/GitLite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases 46 Wiki Activity

Merge remote-tracking branch 'origin/main' into review-center

Browse Source 
# Conflicts:
#	README.md
This commit is contained in:
Christoph
2026-09-07 21:43:57 +02:00
parent f607c6b5cf 25d9d28764
commit 97b5db3031
3 changed files with 0 additions and 167 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
-23
View File
@@ -119,20 +119,6 @@ with the stored credentials.
---
## Development
Start the complete desktop application in development mode with:
```bash
npm run tauri:dev
```
The development launcher preserves normal proxy settings. If a sandboxed
development terminal injects the non-routing `127.0.0.1:9` proxy or its
blocking SSH placeholder, those values are removed only for the Tauri child
process so Git remotes and Git LFS remain testable in the debug application.
---
## Git LFS
@@ -145,12 +131,3 @@ detects LFS usage and automatically downloads the required LFS objects with the
same remote and credentials, so no second pull is needed. Fresh clones also get
repository-local LFS filters and the pre-push hook before they are opened.
---
## SigNoz telemetry
After the user opts in, Gitty sends privacy-filtered product events and technical errors as OTLP/HTTP JSON logs. Every Git/Tauri command is also captured as a trace span with its command name, duration and success state, but without command arguments or results. CPU utilization and resident memory usage of the Gitty process are sampled every 30 seconds and exported as OpenTelemetry gauges. The default endpoints are `https://telemetry.cbsk-tech.de/v1/logs`, `https://telemetry.cbsk-tech.de/v1/traces`, and `https://telemetry.cbsk-tech.de/v1/metrics`.
The SigNoz reverse proxy must forward all three paths to the Collector's OTLP/HTTP receiver (normally port `4318`). For development or a separate collector hostname, set `GITTY_OTLP_LOGS_ENDPOINT`, `GITTY_OTLP_TRACES_ENDPOINT`, and `GITTY_OTLP_METRICS_ENDPOINT` to the full signal URLs before starting Gitty.
Telemetry is non-blocking, bounded, disabled until consent is stored, and never includes repository paths, remote URLs, branch names, commit messages, diffs, file names, credentials, source code, URLs, or email addresses.