Files
Chronos/deploy/docker/entrypoint.sh
T
Alby96andClaude Opus 5.5 f2b58522b9
CI / Build and test (push) Successful in 8m14s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 7s
Release / Build, test and publish (push) Successful in 13m19s
CI / PostgreSQL 16 integration (push) Successful in 4m49s
CI / PostgreSQL 17 integration (push) Successful in 5m28s
CI / Docker image (push) Successful in 53s
Release / Server image (push) Failing after 10s
refactor!: rename Titano to Chronos and move CI and releases to Gitea (#6)
The owner renamed the product and moved the repository to the self-hosted
Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control,
and asked for Actions and a first automatic release with the server package
and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md).

- Chronos everywhere: a byte-exact rename of contents and paths, then a
  per-language review of the forms the old name's ending had dictated.
- Gitea instead of GitHub: the update check, licence, issue and support
  links read ChronosReleasesUrl; the update check takes the highest stable
  version, offers a pre-release build its final release and reports a
  repository it cannot see as a failed check. EULA, security policy and
  Gitea issue forms live at the repository root.
- Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release,
  nightly image and performance gates in the .NET SDK container with git
  checkout and the system SQLite. The release cross-compiles the Windows
  programs, checks their icon, version and DPI manifest, packs installers
  and zips, publishes the Gitea release and pushes the server image
  (REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows
  runner (WINDOWS_RUNNER).
- New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the
  docker-exec script, which Gitea's service containers do not allow; the
  throw-away server runs without durability) and pe-check.
- Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR,
  3 on the shared runner; the weekly performance gates keep theirs).

BREAKING CHANGE: programs, settings, data folders, file types, environment
variables and the Docker image use the new name; nothing is migrated from
Titano, which never had a release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
2026-10-23 12:45:18 +02:00

50 lines
2.1 KiB
Bash
Executable File

#!/bin/sh
# Runs Chronos Server as PUID:PGID (Unraid/NAS convention). The data folder is owned by that user. The archive is left
# as mounted (it may hold terabytes) and only checked for write access; only when that user cannot write it and the
# folder is empty or owned by root (Docker creates a missing bind source or a fresh volume that way) is the folder
# itself, never its contents, given to PUID:PGID.
set -eu
PUID="${PUID:-1000}"
PGID="${PGID:-1000}"
DATA="${CHRONOS_DATA_PATH:-/data}"
ARCHIVE="${CHRONOS_ARCHIVE_PATH:-/archive}"
umask 002
# Help and the health probe touch neither folder.
case "${1:-}" in
--help | -h | -\? | /\? | --healthcheck) exec dotnet /app/Chronos.Server.dll "$@" ;;
esac
as_user() {
setpriv --reuid="$PUID" --regid="$PGID" --clear-groups -- "$@"
}
if [ "$(id -u)" = "0" ]; then
mkdir -p "$DATA" "$ARCHIVE"
chown -R "$PUID:$PGID" "$DATA"
if ! as_user test -w "$ARCHIVE"; then
if [ -z "$(ls -A "$ARCHIVE")" ] || [ "$(stat -c %u "$ARCHIVE")" = "0" ]; then
owner="$(stat -c %u:%g "$ARCHIVE")"
if chown "$PUID:$PGID" "$ARCHIVE" 2>/dev/null; then
echo "chronos: $ARCHIVE belonged to $owner; it now belongs to $PUID:$PGID (the folder only, not its contents)"
fi
fi
if ! as_user test -w "$ARCHIVE"; then
echo "error: $ARCHIVE is not writable by $PUID:$PGID; give that user write access to the archive folder on the host, or set PUID and PGID to its owner" >&2
exit 1
fi
fi
# The server writes into the archive's .chronos folders at once (staging, trash, locks); one left to root by an
# earlier run as root, or copied in by root, would stop it in a restart loop. Reported, never chowned.
for dir in "$ARCHIVE/.chronos" "$ARCHIVE/.chronos"/*/; do
if [ -d "$dir" ] && ! as_user test -w "$dir"; then
echo "error: ${dir%/} is not writable by $PUID:$PGID; give that user write access to it on the host (for example chown -R $PUID:$PGID <archive>/.chronos)" >&2
exit 1
fi
done
exec setpriv --reuid="$PUID" --regid="$PGID" --clear-groups -- dotnet /app/Chronos.Server.dll "$@"
fi
exec dotnet /app/Chronos.Server.dll "$@"