mix/gosentry
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Rename project to GoSentry

Browse Source 
Rename the application, Go module path, command package, build artifacts, resource script, and embedded icon assets from PySentry/pysentry to GoSentry/gosentry.

Move portable settings to gosentry.yaml while reading legacy pysentry.yaml during the transition, then rewrite settings under the new name.

Update Windows and Linux autostart integration to use GoSentry names while cleaning up legacy PySentry registry, desktop-entry, and systemd artifacts.

Refresh README, architecture notes, roadmap, changelog, and release examples for version 0.3.0.
This commit is contained in:
mixeme
2026-06-17 07:29:58 +03:00
parent d828e34121
commit 94033e794f
28 changed files with 182 additions and 112 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ROADMAP.md
+4 -20
View File
@@ -1,22 +1,6 @@
# Roadmap
This file tracks planned PySentry work that is larger than a single bug fix.
## Project Rename
Plan a rename from PySentry to GoSentry.
Rename checklist:
- Decide the final repository path and Go module path.
- Update application name, window title, tray menu, and desktop integration text.
- Update app ID and autostart entry names.
- Rename build artifacts from `pysentry-*` to `gosentry-*`.
- Decide whether runtime files should stay backward-compatible with existing
`pysentry.yaml`, `jobs.yaml`, and log directories or migrate to new names.
- Update README, CHANGELOG, ROADMAP, build scripts, Docker image names, and
package metadata.
- Consider a transition note for users with existing PySentry configuration.
This file tracks planned GoSentry work that is larger than a single bug fix.
## Post-Field-Test Cleanup
@@ -56,7 +40,7 @@ runtime YAML files live next to the executable by default.
Planned delivery variants:
- Windows portable `.zip` with `pysentry.exe`, `README.md`, and `CHANGELOG.md`.
- Windows portable `.zip` with `gosentry.exe`, `README.md`, and `CHANGELOG.md`.
- Linux portable `.tar.gz` archives for `linux-amd64` and `linux-arm64`.
- Debian/Ubuntu `.deb` package once the Linux runtime paths are settled.
- Windows installer later, likely Inno Setup first and MSI/WiX only if needed.
@@ -68,8 +52,8 @@ Packaging design note:
- Portable builds can keep settings and jobs next to the executable.
- Installer/package builds should move runtime data to per-user locations:
`%APPDATA%\PySentry` on Windows, and XDG directories such as
`~/.config/pysentry` and `~/.local/share/pysentry` on Linux.
`%APPDATA%\GoSentry` on Windows, and XDG directories such as
`~/.config/gosentry` and `~/.local/share/gosentry` on Linux.
Initial priority: