brass-and-sigil

minecraft/brass-and-sigil

Fork 0

Commit Graph

Author	SHA1	Message	Date
Matt Sijbers	62c88d4895	fix(deploy): publish manifest.json on Pack-only deploys Stage 5 of Deploy-Brass.ps1 was gated only on \$shouldRunLauncher, so a "-Stage Pack" run regenerated the manifest locally + mirrored pack/overrides/ to the share, but never copied the new manifest.json itself. Result: tweak jars/configs landed on the share, but clients fetching the (still-old) manifest never knew about the new SHA-1s and skipped the re-sync. Caught when fixing the brassandsigil_tweaks jar: the public manifest stayed at 0.9.2 even though local was 0.9.3. Split into two stages -- launcher exe stays gated on \$shouldRunLauncher, manifest.json now publishes whenever \$shouldRunPack (so any Pack, All, or Launcher deploy includes it).	2026-05-09 22:32:01 +01:00
Matt Sijbers	a1331212cb	Initial commit: Brass & Sigil monorepo Self-hosted Minecraft modpack distribution + administration system. - launcher/ Avalonia 12 desktop client; single-file win-x64 publish. Microsoft auth via XboxAuthNet, manifest+SHA-1 mod sync, portable install path, sidecar settings. - server/ brass-sigil-server daemon (.NET 8, linux-x64). Wraps the MC subprocess, embedded Kestrel admin panel with cookie auth + rate limiting, RCON bridge, scheduled backups, BlueMap CLI integration with player markers + skin proxy, friend-side whitelist request flow, world wipe with seed selection (keep current / random / custom). - pack/ pack.lock.json (Modrinth + manual CurseForge entries), data-only tweak source under tweaks/, build outputs in overrides/ (gitignored). - scripts/ Build-Pack / Build-Tweaks / Update-Pack / Check-Updates plus Deploy-Brass.ps1 unified one-shot deploy with version-bump pre-flight and daemon-state detection.	2026-05-05 00:19:05 +01:00

Author

SHA1

Message

Date

Matt Sijbers

62c88d4895

fix(deploy): publish manifest.json on Pack-only deploys

Stage 5 of Deploy-Brass.ps1 was gated only on \$shouldRunLauncher, so a
"-Stage Pack" run regenerated the manifest locally + mirrored
pack/overrides/ to the share, but never copied the new manifest.json
itself. Result: tweak jars/configs landed on the share, but clients
fetching the (still-old) manifest never knew about the new SHA-1s and
skipped the re-sync. Caught when fixing the brassandsigil_tweaks jar:
the public manifest stayed at 0.9.2 even though local was 0.9.3.

Split into two stages -- launcher exe stays gated on \$shouldRunLauncher,
manifest.json now publishes whenever \$shouldRunPack (so any Pack, All,
or Launcher deploy includes it).

2026-05-09 22:32:01 +01:00

Matt Sijbers

a1331212cb

Initial commit: Brass & Sigil monorepo

Self-hosted Minecraft modpack distribution + administration system.

- launcher/  Avalonia 12 desktop client; single-file win-x64 publish.
             Microsoft auth via XboxAuthNet, manifest+SHA-1 mod sync,
             portable install path, sidecar settings.
- server/    brass-sigil-server daemon (.NET 8, linux-x64). Wraps the
             MC subprocess, embedded Kestrel admin panel with cookie
             auth + rate limiting, RCON bridge, scheduled backups,
             BlueMap CLI integration with player markers + skin proxy,
             friend-side whitelist request flow, world wipe with seed
             selection (keep current / random / custom).
- pack/      pack.lock.json (Modrinth + manual CurseForge entries),
             data-only tweak source under tweaks/, build outputs in
             overrides/ (gitignored).
- scripts/   Build-Pack / Build-Tweaks / Update-Pack / Check-Updates
             plus Deploy-Brass.ps1 unified one-shot deploy with
             version-bump pre-flight and daemon-state detection.

2026-05-05 00:19:05 +01:00

2 Commits