primatekuntech/triton-install
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
40 commits 1 branch 0 tags 98 KiB
Commit graph

7 commits

Author SHA1 Message Date
amir-climy
d57345cd74 chore: re-point bootstrapper URLs at Forgejo 
Repo moved to forgejo.primatekun.tech/primatekuntech/triton-install
(public). Swap every raw.githubusercontent.com/primatekuntech/
triton-install/main/* URL inside get.sh and README.md to the
Forgejo raw-content path:

  https://forgejo.primatekun.tech/primatekuntech/triton-install/raw/branch/main/...

End users now run the bootstrapper from Forgejo, anonymously.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-05-31 17:43:59 +08:00
amir-climy
4f2408eeb3 chore: point at forgejo registry + new image name 
Mirror the source-of-truth update from primatekuntech/triton@HEAD:
the Manage Server image now lives at
forgejo.primatekun.tech/primatekuntech/triton-manage-server (not the
legacy ghcr.io/primatekuntech/triton-manageserver). Updates the
distribution copy of compose.yaml, env.template, upgrade.sh plus the
example URLs in get.sh and README.md.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-05-31 12:41:05 +08:00
amir-climy
2c3c2c2863 fix(install): rename install directory from triton-manage-server to triton-manageserver 
Aligns the install directory path with the container image name.
Linux: /opt/triton-manageserver
macOS: ~/.local/share/triton-manageserver

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-05-21 23:28:09 +08:00
amir-climy
e2265c2d89 fix(get.sh): refresh installer files before uninstall 
The uninstall shortcut was executing the stale on-disk uninstall.sh
without refreshing it first, unlike the upgrade path. This meant fixes
to uninstall.sh were never picked up by existing installations.
Refresh all installer files before exec-ing uninstall.sh.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-05-19 19:58:02 +08:00
amir-climy
bacccd9550 feat: add --upgrade one-liner and improve upgrade.sh 
get.sh --upgrade:
- Re-downloads installer files (compose.yaml, upgrade.sh, etc.) so the
  on-disk scripts are always current before upgrading
- Then execs upgrade.sh with any passthrough flags (e.g. --image TAG)

upgrade.sh improvements:
- Platform-aware backup dir (Linux: /var/backups/triton,
  macOS: ~/Library/Application Support/triton/backups)
- Reads POSTGRES_USER/POSTGRES_DB from .env instead of hardcoding
- Uses detected runtime (podman/docker) for pg_dump exec
- Explicit messaging that DB migrations run automatically on startup
- Health check success confirms migrations applied
- Prints rollback command pointing at the backup file

Usage:
  curl -fsSL .../get.sh | sudo bash -s -- --upgrade
  curl -fsSL .../get.sh | sudo bash -s -- --upgrade --image ...:1.2.0

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-05-19 19:19:57 +08:00
amir-climy
ffa10f9171 feat(get.sh): add --uninstall flag for one-liner uninstall 
curl -fsSL .../get.sh | sudo bash -s -- --uninstall
  curl -fsSL .../get.sh | sudo bash -s -- --uninstall --purge-data

Detects --uninstall early, resolves INSTALL_DIR from platform, and
execs the on-disk uninstall.sh (passing --purge-data through).
Fails fast with a clear message if Triton is not installed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-05-19 19:11:35 +08:00
amir-climy
6ff24df8d1 feat(installer): add one-liner bootstrap script for Manage Server 
Adds get.sh — a curl-piped installer that:
- Detects Linux vs macOS
- Checks for Podman/Docker + compose runtime
- Installs Podman automatically (apt/dnf/yum/zypper/pacman on Linux, Homebrew on macOS)
- Falls back to pip3 for podman-compose when not in package manager
- Downloads installer files to /opt/triton-manage-server (Linux) or
  ~/.local/share/triton-manage-server (macOS)
- Delegates to install.sh with all forwarded flags

Usage:
  curl -fsSL https://raw.githubusercontent.com/primatekuntech/triton-install/main/get.sh | sudo bash

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-05-18 13:27:06 +08:00