Files

T

omar 0932e16178 docs: drop internal upstream fork-monitoring notes

Remove upstream-forks.md and upstream-hefengfan0615-evaluation.md (the
original maintainer's fork-tracking notes, irrelevant to this deployment)
and their references in the docs index and contributing guide.

2026-06-02 22:23:33 +03:00

2.9 KiB

Raw Permalink Blame History

Contributing Guide

Thanks for your interest in contributing to DS2API!

Development Setup

Prerequisites

Go 1.26+
Node.js 20.19+ or 22.12+ (for WebUI development)
npm (bundled with Node.js)

Backend Development

# 1. Clone
git clone https://github.com/CJackHwang/ds2api.git
cd ds2api

# 2. Configure
cp config.example.json config.json
# Edit config.json with test accounts

# 3. Run backend
go run ./cmd/ds2api
# Local access: http://127.0.0.1:5001
# Actual bind: 0.0.0.0:5001, so LAN access is available via your private IP

Frontend Development (WebUI)

# 1. Navigate to WebUI directory
cd webui

# 2. Install dependencies
npm install

# 3. Start dev server (hot reload)
npm run dev
# Default: http://localhost:5173, auto-proxies API to backend
# host: 0.0.0.0 is not configured, so LAN access is not enabled by default

WebUI tech stack:

React + Vite
Tailwind CSS
Bilingual language packs: webui/src/locales/zh.json / en.json

Docker Development

docker-compose -f docker-compose.dev.yml up

Code Standards

Language	Standards
Go	Run `gofmt -w` after editing Go files; before committing, run `./scripts/lint.sh` (format check + golangci-lint)
JavaScript/React	Follow existing project style (functional components)
Commit messages	Use semantic prefixes: `feat:`, `fix:`, `docs:`, `refactor:`, `style:`, `perf:`, `chore:`

Do not silently ignore cleanup errors from I/O-style calls such as Close, Flush, or Sync; return them when possible, otherwise log them explicitly.

Submitting a PR

Fork the repo
Create a branch (e.g. feature/xxx or fix/xxx)
Commit changes
Push your branch
Open a Pull Request

💡 If you modify files under webui/, no manual build is needed — CI handles it automatically. If you want to verify the generated static/admin/ assets locally, you can still run ./scripts/build-webui.sh.

Build WebUI

Manually build WebUI to static/admin/:

./scripts/build-webui.sh

Running Tests

# Local PR gates (kept aligned with the quality-gates workflow)
./scripts/lint.sh
./tests/scripts/check-refactor-line-gate.sh
./tests/scripts/run-unit-all.sh
npm run build --prefix webui

# End-to-end live tests (real accounts; recommended for releases or high-risk changes)
./tests/scripts/run-live.sh

Project Structure

To avoid documentation drift, directory layout and module responsibilities were moved to:

Before contributing, review the architecture doc sections for request flow and internal/ module boundaries.

Reporting Issues

Please use GitHub Issues and include:

Steps to reproduce
Relevant log output
Environment info (OS, Go version, deployment method)

2.9 KiB Raw Permalink Blame History