Files
Chronos/deploy/docker/Dockerfile
T
Alby96andClaude Opus 5.5 5f27a86406
CI / Build and test (pull_request) Failing after 2m3s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 4s
refactor!: rename Titano to Chronos and move CI and releases to Gitea
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. 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) and
  pe-check.

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>
2026-10-23 11:34:48 +02:00

46 lines
1.9 KiB
Docker

# Chronos Server — multi-stage, multi-arch (linux/amd64, linux/arm64). BRIEF §14.9.
FROM --platform=$BUILDPLATFORM mcr.microsoft.com/dotnet/sdk:10.0 AS build
ARG TARGETARCH
ARG CHRONOS_VERSION=0.0.0-dev
WORKDIR /src
COPY global.json Directory.Build.props Directory.Build.targets Chronos.slnx ./
COPY i18n/ i18n/
COPY src/Chronos.Core/ src/Chronos.Core/
COPY src/Chronos.Data/ src/Chronos.Data/
COPY src/Chronos.Protocol/ src/Chronos.Protocol/
COPY src/Chronos.Server/ src/Chronos.Server/
RUN dotnet publish src/Chronos.Server/Chronos.Server.csproj \
-c Release -a "$TARGETARCH" --no-self-contained \
-p:ChronosVersion="$CHRONOS_VERSION" -o /out \
&& rm -f /out/*.pdb
FROM mcr.microsoft.com/dotnet/aspnet:10.0
ARG CHRONOS_VERSION=0.0.0-dev
LABEL org.opencontainers.image.title="Chronos Server" \
org.opencontainers.image.description="Time-lapse archive, uploads, jobs and rendering server" \
org.opencontainers.image.version="$CHRONOS_VERSION" \
org.opencontainers.image.licenses="LicenseRef-Chronos-EULA"
# ASPNETCORE_HTTP_PORTS is emptied: the server binds its own ports, and the base image's 8080 only made Kestrel warn
# "Overriding address(es)" at every start.
ENV CHRONOS_ARCHIVE_PATH=/archive \
CHRONOS_DATA_PATH=/data \
CHRONOS_HTTP_PORT=8080 \
CHRONOS_HTTPS_PORT=8443 \
CHRONOS_DB=postgres \
PUID=1000 \
PGID=1000 \
ASPNETCORE_HTTP_PORTS= \
DOTNET_gcServer=1 \
DOTNET_GCHeapAffinitizeMask= \
DOTNET_NOLOGO=1
WORKDIR /app
COPY --from=build /out/ ./
COPY deploy/docker/entrypoint.sh /usr/local/bin/chronos-entrypoint
RUN chmod 0755 /usr/local/bin/chronos-entrypoint && mkdir -p /archive /data
VOLUME ["/archive", "/data"]
EXPOSE 8080 8443
HEALTHCHECK --interval=30s --timeout=8s --start-period=40s --retries=3 \
CMD ["dotnet", "/app/Chronos.Server.dll", "--healthcheck"]
ENTRYPOINT ["/usr/local/bin/chronos-entrypoint"]