mirror of
https://github.com/J3vb/OwnCord.git
synced 2026-09-03 03:50:00 +03:00
release: v1.2.0-alpha.2 (#1333)
* docs: add bug-detection improvements plan
Plan for mechanical bug detection alongside the agentic hunt: activate the 14
unused Go fuzz harnesses, the configured-but-never-run Stryker setup, and
browser-mode vitest; encode recurring bug classes as semgrep rules; add
model-based and fault-injected ordering tests; add a persistent seen-ledger
and sibling-sweep lens to the hunt.
All local-only and on demand - fuzz crashers are working reproducers, and this
repo is public.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* build: add make fuzz target and ignore mutation-test output
`go test ./...` runs each Fuzz* function against its committed seed corpus
only - one pass per seed, zero generated inputs - so the 17 fuzz harnesses in
Server/ have never actually fuzzed. `make fuzz` enumerates every target and
runs each with a time budget (Go fuzzes one target per package per
invocation, hence the loop). Local-only by design: a crasher is a working
reproducer and this repo is public.
Also gitignore Client/tauri-client/.stryker-tmp/ and reports/ - a Stryker run
left 200+ untracked files, and a surviving-mutant report maps exactly which
behaviour nothing tests.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* test(client): pin reconnect auth-frame and replay-dedup arming
Stryker found 14 surviving mutants across ws.ts:413/422/428 - the auth frame
built on reconnect. Every condition there could be flipped with all 4777
tests still green: the replay-dedup arming guard, the resume-vs-fresh-connect
ternary, and the conditional active_channel_id spread.
Seven tests through the public send/isReplaying surface, no new exports. Two
isolate each half of the `reconnectAttempt > 0 && lastSeq > 0` AND condition -
the combination no existing test reached, and the one an && -> || mutant
walked straight through.
Verified by flipping the line 413 guard to `if (true)`: 3 of 7 fail, revert
restores green.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: record two fuzz corpus traps
Interrupting a fuzz run manufactures a false crasher: Go cannot distinguish a
worker that crashed on an input from one killed externally, so it saves the
in-flight input to testdata/fuzz/ as a suspect. It looks exactly like a real
security finding. Replay before believing it.
And committed seed corpus shares the testdata/fuzz/<Target>/ directory with
any false crasher, so clearing one by removing the directory deletes the
seeds too.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat(client): enforce three prose invariants as ESLint rules
CLAUDE.md documents the voice-supersession, E2EE staleness and dispatcher
invariants in English. English fails no build, and bug hunts keep rediscovering
the same classes. Five rules encode them as an inline flat-config plugin - no
new dependency, and `npx eslint src/` is already a blocking CI gate.
- no-leave-voice-when-superseded: a global leaveVoice() inside a branch that
already confirmed supersession tears down the newer live session
- e2ee-epoch-needs-keypair-check: a non-key-holder never bumps the epoch, so
an epoch-only staleness guard cannot see a restarted session
- e2ee-verified-status-literal: keeps "verified" tied to a hand-written call
site that earned it, never a computed status
- no-identity-scope-fallback: a `?? 0` placeholder scope mints a keypair under
the wrong account
- no-store-write-in-ws-on: page-local ws.on handlers may read stores, not
write them
Each rule proven to fire by reintroducing the historical bug shape and
reverting; RuleTester cases cover both the real shapes that must stay clean
and the bug shapes that must not.
A fourth candidate - await-then-stale-snapshot - was declined as not
AST-expressible: whether an await needs a guard, and whether the guard is
sufficient, is intent rather than shape, and the rule would flag most of the
already-correct guard code in livekitSession.ts.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: correct dispatcher invariant, record Tier 2 as shipped
The client CLAUDE.md claimed ws.on(...) appears only in dispatcher.ts. Eight
handlers across main.ts, MainPage.ts and ChannelController.ts say otherwise -
page-local UI (ringing, overlays, slow-mode timers) legitimately subscribes.
The real invariant is narrower: dispatcher is the single path by which server
events WRITE to domain stores. That is what local/no-store-write-in-ws-on
enforces, and the doc now matches the code.
Also record that Tier 2 shipped as ESLint rules rather than semgrep, and why
the fourth candidate was declined.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(client): move the status-picker dot onto the avatar corner
The corner dot on the user bar avatar was a static hardcoded-green div —
never reflected real status and did nothing on click. Removed it and
relocated the actual StatusPicker trigger dot (real color, opens the
status dropdown) to that same corner instead of its own row. The
"Online"/"Idle"/... text label under the username is unchanged.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* fix(client): return the saved password over IPC again
The remember-password box saved a password the client could never read
back. Hardening had put #[serde(skip)] on CredentialData::password, so
load_credential returned a record whose password was always absent and
the login form could not prefill it — the box appeared to work and
silently did nothing.
Drop the skip and carry the field through the TS wrapper, which now maps
a non-string password to undefined rather than trusting the payload.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* feat(client): add an auto-connect checkbox to the login form
Auto-connect already existed end to end — ServerProfile.autoConnect,
setAutoLogin(), and the boot auto-login block with its cancel overlay —
but was only reachable through the zap button on a server card. This
surfaces the same state as a checkbox under Remember password, where
users look for it.
Ticking it forces Remember password on and disables it: boot auto-login
replays the stored token, which saveCredential only writes when the
password is remembered, so the two cannot be set independently without
producing a setting that silently does nothing.
Unticking is guarded. setAutoLogin(null) clears autoConnect on every
profile, so a bare toggle-off would wipe another server's setting; the
clear now only fires when this profile is the current holder. The guard
lives in ensureProfileExists, which all four auth paths already route
through.
Also consume the password restored in the previous commit, so selecting
a saved server prefills it instead of leaving the field blank.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* chore(release): bump client to 1.2.0-alpha.2
The client version is not derived from the tag — release.yml's
verify-versions job compares the tag against package.json and
tauri.conf.json and fails the release if they drift, so all five
manifests (both lockfiles included) move together.
Also refreshes the literal version in the README and docs build
examples, and closes the Unreleased changelog section as v1.2.0-alpha.2.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* docs(changelog): record the three bug-hunt sweeps in v1.2.0-alpha.2
PRs #1328, #1331 and #1332 merged to main after v1.2.0-alpha.1 was tagged
and closed 233 verified defects between them, but none of the three left
an entry in the curated changelog — the generated list covers commits,
this file covers behaviour, and nothing bridged the two.
Verified unreleased by ancestry rather than by date (none of the three
merge commits is an ancestor of v1.2.0-alpha.1), so all of it ships for
the first time in alpha.2.
Nine entries grouped by subsystem, leading with the changes an operator
or user would actually notice: the 24h-retention desync, the avatar-
deleting orphan sweep, the zero-byte restore truncation, the six hot-mic
paths, and the TOFU re-pin that would have warned every install at once.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
* test(client): drop the e2e assertion for the removed user-bar status dot (#1334)
26b46cc removed the hardcoded-green `.status-dot` div from the user bar
avatar and relocated the real StatusPicker trigger dot into that corner,
adding "status picker dot sits on the avatar" to cover the new element.
The old "user bar has status dot" test was left behind and now fails on
an element that no longer exists by design.
The replacement test already asserts the corner dot is present and
visible, so removing the stale one loses no coverage.
Claude-Session: https://claude.ai/code/session_01Rkv9dVo5YEYArqrDRfW41w
Co-authored-by: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
J3vb
+1
-1
@@ -1973,7 +1973,7 @@ Owner-only self-update from GitHub Releases (minisign/Ed25519-verified; see
|
||||
|
||||
```json
|
||||
{
|
||||
"current": "v1.2.0-alpha.1",
|
||||
"current": "v1.2.0-alpha.2",
|
||||
"latest": "v1.2.0",
|
||||
"update_available": true,
|
||||
"required_assets_present": true,
|
||||
|
||||
+2
-2
@@ -16,13 +16,13 @@ Production deployment guide for OwnCord server on Windows and Linux.
|
||||
**Windows:**
|
||||
```bash
|
||||
cd Server
|
||||
go build -o chatserver.exe -ldflags "-s -w -X main.version=1.2.0-alpha.1" .
|
||||
go build -o chatserver.exe -ldflags "-s -w -X main.version=1.2.0-alpha.2" .
|
||||
```
|
||||
|
||||
**Linux:**
|
||||
```bash
|
||||
cd Server
|
||||
CGO_ENABLED=0 go build -o chatserver -ldflags "-s -w -X main.version=1.2.0-alpha.1" .
|
||||
CGO_ENABLED=0 go build -o chatserver -ldflags "-s -w -X main.version=1.2.0-alpha.2" .
|
||||
```
|
||||
|
||||
- `-s -w` strips debug info (smaller binary)
|
||||
|
||||
@@ -0,0 +1,265 @@
|
||||
# Bug-detection improvements — design
|
||||
|
||||
Date: 2026-08-08
|
||||
Status: approved, not implemented
|
||||
|
||||
## Problem
|
||||
|
||||
The multi-agent bug hunt finds real defects at a high rate — the 2026-08-08
|
||||
client hunt confirmed 88 bugs and the follow-up sweeps fixed 101 — but it is
|
||||
the only mechanism doing so, it costs a large token budget per run, and it has
|
||||
never converged. Meanwhile several bug-catching tools are already installed,
|
||||
configured, and committed to this repository, and none of them execute.
|
||||
|
||||
This design adds mechanical detection alongside the agentic hunt, prioritised
|
||||
by yield per token spent.
|
||||
|
||||
## What already exists and does not run
|
||||
|
||||
| Asset | State | Gap |
|
||||
| --- | --- | --- |
|
||||
| 14 `Fuzz*` harnesses under `Server/**/*_fuzz_test.go` | Committed | `go test ./...` runs a `Fuzz*` function against its **seed corpus only** — one pass per seed, zero generated inputs. `-fuzz` appears nowhere in the repo. |
|
||||
| Stryker mutation testing | `stryker.config.mjs` + `npm run test:mutate` | Referenced in `ci.yml` only inside an npm-audit comment. Has never run. |
|
||||
| Browser-mode vitest | `vitest.config.browser.ts` + `npm run test:browser` | CI runs jsdom only. |
|
||||
| Cross-package coverage | `make cover-all` prints every 0.0%-covered function | Output is not fed to anything. |
|
||||
|
||||
Separately, three of the codebase's sharpest invariants are documented in
|
||||
`CLAUDE.md` files as prose and asserted nowhere:
|
||||
|
||||
- `ws`: "a frame that skips the queue, or a seq allocated for a frame that is
|
||||
then dropped, is silently unrecoverable"
|
||||
- voice: cleanup in an aborted attempt "must be scoped to that attempt's own
|
||||
room — a global `leaveVoice()` there kills the live session"
|
||||
- E2EE: "must never report an unverified peer as verified"
|
||||
|
||||
Prose fails no build.
|
||||
|
||||
## Locked decisions
|
||||
|
||||
**Everything in this design runs locally, on demand. Nothing is added to
|
||||
GitHub Actions.**
|
||||
|
||||
Rationale: `go test -fuzz` writes each crashing input to
|
||||
`testdata/fuzz/<Target>/<hash>`, and that file *is* a working reproducer. The
|
||||
root `CLAUDE.md` states: "This repo is public — unfixed defects do not belong
|
||||
in commits, issues, or PR descriptions." Actions artifacts on a public repo are
|
||||
downloadable by anyone, and a red scheduled job is itself a public signal that
|
||||
something is broken. A Stryker surviving-mutant report is a milder version of
|
||||
the same disclosure: a precise map of which behaviour nobody tests.
|
||||
|
||||
Local-only also means zero new workflow files and zero CI minutes.
|
||||
|
||||
**Corpus discipline.** A crasher stays uncommitted until its fix exists. The
|
||||
`testdata/fuzz/` corpus entry and the fix are committed together, as one
|
||||
regression test. This is the same shape as the existing test-first rule.
|
||||
|
||||
**Always replay a crasher before believing it.** Go runs fuzz targets in
|
||||
separate worker processes. When a worker dies without reporting, the
|
||||
coordinator cannot tell "crashed on this input" from "was killed externally",
|
||||
so it saves the in-flight input to `testdata/fuzz/` as a suspected crasher.
|
||||
Interrupting a fuzz run therefore manufactures a fake reproducer that is
|
||||
indistinguishable at a glance from a real security finding. Confirm with
|
||||
`go test ./<pkg> -run='<FuzzTarget>'` — a real crasher fails there. Observed
|
||||
2026-08-08: a 1666-byte malformed JPEG appeared under
|
||||
`api/testdata/fuzz/FuzzImageDimensions/` purely because the run was killed.
|
||||
|
||||
**Never `rm -r` a `testdata/fuzz/<Target>/` directory** to clear a false
|
||||
crasher. Committed seed corpus files live in the same directory — deleting the
|
||||
directory takes them with it. Remove the single offending file by name.
|
||||
|
||||
**Superseded 2026-08-08: Tier 2 ships as ESLint rules, not semgrep.** Semgrep
|
||||
has no native Windows support (WSL or Docker only), so on this machine it would
|
||||
join `make` as tooling that cannot be run locally. ESLint flat config supports
|
||||
an inline plugin, so custom rules cost no new dependency — and `npx eslint
|
||||
src/` is already a blocking CI gate, which removes the promotion step entirely.
|
||||
Rules live in `Client/tauri-client/eslint-rules.js`, tested with `RuleTester`
|
||||
in `tests/unit/eslint-rules.test.ts`. See "Tier 2 — delivered" below.
|
||||
|
||||
## Tier 1 — Turn on what already exists
|
||||
|
||||
### 1a. `make fuzz`
|
||||
|
||||
Go fuzzes **one target per package per invocation**, so this cannot be a single
|
||||
`go test -fuzz ./...`. The target enumerates fuzz functions and runs each with
|
||||
a time budget.
|
||||
|
||||
Add to `Server/Makefile`, and to its header comment block:
|
||||
|
||||
```make
|
||||
# fuzz Actually fuzz. CI only replays the seed corpus; this generates inputs.
|
||||
# Override the per-target budget: FUZZTIME=2m make fuzz
|
||||
FUZZTIME ?= 30s
|
||||
fuzz:
|
||||
@for pkg in $$(go list ./...); do \
|
||||
for fn in $$(go test -list='^Fuzz' $$pkg 2>/dev/null | grep '^Fuzz'); do \
|
||||
echo "── $$pkg $$fn"; \
|
||||
go test $$pkg -run='^$$' -fuzz="^$$fn$$" -fuzztime=$(FUZZTIME) || exit 1; \
|
||||
done; \
|
||||
done
|
||||
```
|
||||
|
||||
Add `fuzz` to the `.PHONY` list.
|
||||
|
||||
Default budget 30s per target — a full sweep of 14 targets is about 10 minutes
|
||||
unattended. `FUZZTIME=2m` for a deep run.
|
||||
|
||||
### 1b. Scoped Stryker runs
|
||||
|
||||
`stryker.config.mjs` already scopes mutation to `src/lib/**` and `src/stores/**`
|
||||
with `thresholds.break: 50`. A full run over that scope is expensive; a
|
||||
hotspot run is not:
|
||||
|
||||
```bash
|
||||
npx stryker run --mutate "src/lib/dispatcher.ts,src/lib/ws.ts,src/lib/livekitE2EE.ts"
|
||||
```
|
||||
|
||||
Roughly 25 minutes for three files. Surviving mutants identify lines whose
|
||||
behaviour can be changed with the entire 4800-test suite still green.
|
||||
|
||||
Treat the result as advisory. Do not gate on `thresholds.break` — the threshold
|
||||
in the config file applies to a full-scope run and is meaningless for a
|
||||
three-file subset.
|
||||
|
||||
Target the files the hunt keeps returning to: `dispatcher.ts`, `ws.ts`,
|
||||
`livekitE2EE.ts`, `identity.ts`, and the voice session module.
|
||||
|
||||
### 1c. Browser-mode vitest
|
||||
|
||||
Run `npm run test:browser` locally. The client `CLAUDE.md` already documents
|
||||
jsdom diverging from native Web Storage semantics; browser mode is the only
|
||||
configured surface that observes that class.
|
||||
|
||||
### 1d. Prerequisite
|
||||
|
||||
Confirm `Client/tauri-client/reports/`, `Client/tauri-client/.stryker-tmp/`,
|
||||
`Server/coverage-all.out`, and `Server/**/testdata/fuzz/` interim output are
|
||||
covered by `.gitignore` before running any of the above. Add entries where
|
||||
they are missing.
|
||||
|
||||
## Tier 2 — Bugs to permanent detectors
|
||||
|
||||
Roughly 200 confirmed real bugs have been fixed across the hunt and harvest
|
||||
runs. Each one currently bought exactly one fix. Encoding the recurring
|
||||
*classes* converts them into permanent detectors.
|
||||
|
||||
**Sources to mine:** bughunt commit history on `fix/bughunt-*` and
|
||||
`fix/bughunt-harvest-*` branches, `.superpowers/harvest-med-low-checklist.md`,
|
||||
and `docs/audit-*.md`.
|
||||
|
||||
**Method:** cluster findings by class, not by symptom. Use the installed
|
||||
`semgrep-rule-creator` skill, which is test-first — each rule ships with a
|
||||
positive fixture that must match and a negative fixture that must not.
|
||||
|
||||
### Tier 2 — delivered 2026-08-08
|
||||
|
||||
Five rules, all scoped to the modules their invariant governs, all proven to
|
||||
fire by reintroducing the historical bug shape into real source and reverting:
|
||||
|
||||
| Rule | Encodes |
|
||||
| --- | --- |
|
||||
| `no-leave-voice-when-superseded` | A global `leaveVoice()` inside a branch that already confirmed supersession tears down the newer live session |
|
||||
| `e2ee-epoch-needs-keypair-check` | A non-key-holder never bumps the epoch, so an epoch-only staleness guard cannot see a restarted session |
|
||||
| `e2ee-verified-status-literal` | Keeps `"verified"` tied to a hand-written call site that earned it, never a computed status |
|
||||
| `no-identity-scope-fallback` | A `?? 0` placeholder scope mints a keypair under the wrong account |
|
||||
| `no-store-write-in-ws-on` | Page-local `ws.on` handlers may read stores, not write them |
|
||||
|
||||
**Declined: `await`-then-stale-snapshot.** Not AST-expressible. Whether an
|
||||
await needs a guard — and whether the guard present is sufficient and correctly
|
||||
placed — is intent, not shape. `livekitSession.ts` alone expresses supersession
|
||||
guards in at least four different forms, and several awaits legitimately need
|
||||
no guard. Any rule here would be too narrow to catch real bugs or broad enough
|
||||
to flag most of the file's already-correct guard code. A rule that misfires on
|
||||
correct code gets disabled and trains people to ignore the linter.
|
||||
|
||||
**Found while writing these:** the dispatcher invariant in the client
|
||||
`CLAUDE.md` was factually wrong. It claimed `ws.on(...)` appears only in
|
||||
`dispatcher.ts`; eight handlers across `main.ts`, `MainPage.ts` and
|
||||
`ChannelController.ts` say otherwise. The true invariant — dispatcher is the
|
||||
single path by which server events *write to stores* — is what the rule
|
||||
encodes, and the doc has been corrected to match.
|
||||
|
||||
**Still open:** the server-side `ws` seq/FIFO invariant, which needs a Go
|
||||
runtime assertion rather than a lint rule.
|
||||
|
||||
Not every fixed bug becomes a rule. A class earns one when it has recurred at
|
||||
least twice, or when it corresponds to an invariant already written down in a
|
||||
`CLAUDE.md`.
|
||||
|
||||
## Tier 3 — Stateful and chaos testing
|
||||
|
||||
Fuzzing and property tests find bad **functions**. Every recurring bug in this
|
||||
codebase's history is a bad **ordering**: `registerNow` reconnect-transfer,
|
||||
superseded voice sessions, duplicate-message reconciliation, resync corruption,
|
||||
the auth-race deep link, the logout/auto-login race. Nothing in the repo
|
||||
generates orderings.
|
||||
|
||||
### 3a. Client model-based tests
|
||||
|
||||
`fast-check` v4 is already a dependency, and
|
||||
`tests/unit/*.property.test.ts` establish the house pattern. Use `fc.commands`.
|
||||
|
||||
- **Commands:** `Connect`, `Disconnect`, `RegisterNow`, `Receive(seq)`,
|
||||
`Supersede`, `Resync`, `Logout`.
|
||||
- **Model:** a minimal reference implementation of expected store state — not
|
||||
a second copy of the real logic.
|
||||
- **Invariants:** message ids never duplicate; per-client seq is monotonic; a
|
||||
verified peer never flips to unverified and back; an aborted voice attempt
|
||||
never tears down a live session owned by a newer attempt.
|
||||
|
||||
The shrinking is the point: fast-check reduces a 40-step failure to the minimal
|
||||
3-step reproducer, which is what makes an ordering bug fixable at all.
|
||||
|
||||
### 3b. Server hub simulation
|
||||
|
||||
A `ws` package test driving random interleavings of subscribe, broadcast, ack
|
||||
and disconnect under `-race`, asserting the FIFO and seq property already
|
||||
stated in `Server/CLAUDE.md`. Seeded and therefore replayable.
|
||||
|
||||
### 3c. Fault-injected transport
|
||||
|
||||
A test-only wrapper that drops, reorders, duplicates and delays frames from a
|
||||
seed. Shared by 3a and 3b. Deterministic: a failing seed reproduces exactly.
|
||||
|
||||
## Tier 4 — Sharpen the hunt
|
||||
|
||||
The 2026-08-08 client hunt fixed 101 bugs and still did not converge. Four
|
||||
changes, cheapest first:
|
||||
|
||||
1. **Persistent seen-ledger.** Key on `(file, symbol, class)` and persist
|
||||
*across* runs, not only within one. Each run currently starts cold and
|
||||
re-derives ground already covered — the most likely reason convergence never
|
||||
arrives.
|
||||
2. **Sibling-sweep lens.** For every confirmed bug, enumerate the other callers
|
||||
of the touched function. This is the root-cause rule turned into a lens: it
|
||||
converts one finding into its whole family, which is also what stops the
|
||||
same class reappearing in the next round.
|
||||
3. **Coverage-guided targeting.** `make cover-all` already prints every
|
||||
function at 0.0%. Feed that list to the finders as a priority surface.
|
||||
4. **Anti-pattern priming.** Supply the fixed-bug corpus as "confirmed-real
|
||||
classes in this codebase — hunt siblings" rather than starting each finder
|
||||
from a cold read.
|
||||
|
||||
## Order and effort
|
||||
|
||||
| Step | Effort | Runs in |
|
||||
| --- | --- | --- |
|
||||
| 1a `make fuzz` | 15 min to write | 10 min/sweep unattended |
|
||||
| 1b Stryker hotspots | 0 (already configured) | ~25 min for 3 files |
|
||||
| 1d gitignore check | 5 min | — |
|
||||
| 2 first four semgrep rules | ~1 afternoon | seconds |
|
||||
| 4.1 + 4.2 ledger and sibling lens | ~2 hours | within existing hunt |
|
||||
| 1c browser-mode vitest | 0 | minutes |
|
||||
| 3 model-based and chaos harnesses | ~1 day | minutes |
|
||||
|
||||
Tier 1a is first because 14 harnesses — the expensive part — are already
|
||||
written and produce nothing today.
|
||||
|
||||
## Non-goals
|
||||
|
||||
- No new GitHub Actions workflows, jobs, or scheduled runs.
|
||||
- No gating of any existing CI check on mutation score or fuzz results.
|
||||
- No change to the existing test suites' assertions. The client suite is green
|
||||
and stays green.
|
||||
- No promotion of semgrep to CI in this scope.
|
||||
- No replacement of the agentic bug hunt. Tier 4 sharpens it; Tiers 1 to 3 run
|
||||
beside it.
|
||||
+2
-2
@@ -55,11 +55,11 @@ Full Docker details: [Deployment Guide](deployment.md#docker-linux).
|
||||
```bash
|
||||
# Server (Windows)
|
||||
cd Server
|
||||
go build -o chatserver.exe -ldflags "-s -w -X main.version=1.2.0-alpha.1" .
|
||||
go build -o chatserver.exe -ldflags "-s -w -X main.version=1.2.0-alpha.2" .
|
||||
|
||||
# Server (Linux)
|
||||
cd Server
|
||||
CGO_ENABLED=0 go build -o chatserver -ldflags "-s -w -X main.version=1.2.0-alpha.1" .
|
||||
CGO_ENABLED=0 go build -o chatserver -ldflags "-s -w -X main.version=1.2.0-alpha.2" .
|
||||
|
||||
# Client
|
||||
cd Client/tauri-client
|
||||
|
||||
Reference in New Issue
Block a user