dev

文件	最后提交记录	最后更新时间
ci.yml	chore: rename project InfoSphere to KnowForge Rename the project throughout the codebase: brand strings InfoSphere -> KnowForge and identifiers infosphere -> knowforge. This includes the Go module path (infosphere/server -> knowforge/server) and all imports, the auth cookie name (infosphere_token -> knowforge_token; existing sessions must re-login), package names, deploy unit/env/sudoers filenames, the Android package org.devlive.knowforge, and external repo/registry/domain references. Generated build artifacts and lockfiles are left untouched. The logo and favicon assets were replaced separately.	4 天前
deploy.yml	fix(compat): keep the KnowForge rename backward-compatible with existing deploys The rename broke upgrades of a live infosphere deployment. Make it seamless instead of forcing secret/env/data changes: - Startup bridges legacy INFO_SPHERE_* env vars to KNOWFORGE_* (new wins), so an existing env file keeps working unchanged. - CI Assemble step falls back to the INFO_SPHERE_ENV_FILE secret when KNOWFORGE_ENV_FILE is not set, fixing the empty-secret build failure. - systemd ReadWritePaths allows both /var/lib/knowforge and the existing /var/lib/infosphere, so data stays in place with no forced migration. - Auth reads the legacy infosphere_token cookie as a fallback so live sessions are not logged out on upgrade; logout clears both cookies. 137 tests pass.	4 天前
release.yml	chore: rename project InfoSphere to KnowForge Rename the project throughout the codebase: brand strings InfoSphere -> KnowForge and identifiers infosphere -> knowforge. This includes the Go module path (infosphere/server -> knowforge/server) and all imports, the auth cookie name (infosphere_token -> knowforge_token; existing sessions must re-login), package names, deploy unit/env/sudoers filenames, the Android package org.devlive.knowforge, and external repo/registry/domain references. Generated build artifacts and lockfiles are left untouched. The logo and favicon assets were replaced separately.	4 天前