0 Fork 0

Files

T

Lucas RayanandClaude Sonnet 5.5 a4a2584f37 #14 : Gitea CI, registry composes, Node 22 image and changelog

- Gitea Actions: Trivy, Vitest in a Dockerfile test stage, arm64 image build, image
  scan and smoke test; releases reuse the image by content hash.
- docker-compose.<edition>.registry.yaml run the stack from the published image.
- Dockerfile: Node 22, a test stage, and no npm in the runtime image.
- README, CLAUDE.md and CHANGELOG describe the CI, the image and the release flow.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

2026-11-01 22:54:00 -03:00

1.9 KiB

Raw Blame History

Changelog

Everything notable in CraftDock is recorded here. The format follows Keep a Changelog and the project follows Semantic Versioning.

Unreleased

0.1.0 - 2026-11-01

First versioned release. It collects the state of CraftDock on 2026-11-01.

Added

Web panel to manage a single Minecraft server (Java or Bedrock) running as a Docker container: start / stop / restart / kill, live CPU, RAM and player count, real-time console over WebSocket, server.properties editor, world download / upload / regeneration, seed and seed map, and a persistent player directory with a per-player inspector (position, health, inventory, XP) read from the world save (Java playerdata, Bedrock LevelDB).
Adapter layer for the two editions (Java over RCON, Bedrock over docker attach).
Structured JSON logging, a bcrypt-authenticated session on every route and socket, and a self-healing healthcheck.
docker-compose.<edition>.registry.yaml, which runs the stack from the published image.
A CI on the Gitea runners (.gitea/workflows): Trivy on the repository and on the image, the Vitest suite, an arm64 image build and a smoke test. The image is built once per content hash and reused by the release.
CHANGELOG.md.

Changed

The code, the container image and the releases now live on Gitea (git.lucasrguerra.dev.br); the deployment pulls the image from its registry.
Dockerfile: Node 20 → 22; a dedicated test stage runs the suite on the same compiled dependencies; the runtime image no longer carries npm.
The repository history was lost with the previous GitHub account, so this repository starts from a fresh history at the 2026-11-01 state.
.gitattributes forces LF line endings.