dev

文件	最后提交记录	最后更新时间
knowforge-api.service	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.	23 天前
knowforge.env.example	fix(deploy): finish rename to KNOWFORGE_ env vars and migrate old data dir Complete the rebrand for runtime configuration: rename the INFO_SPHERE_* environment variables (INFO_SPHERE_DATA, _PORT, _WEB_PORT, _STATIC_ROOT, _API_URL, _UPGRADE, _UPSTREAM_REPO, _TRUSTED_PROXIES, _SITE_URL, _ENV_FILE) to KNOWFORGE_* across code, tests, deploy unit/env, Docker and docs, and the deploy secret to KNOWFORGE_ENV_FILE. The upgrade failed because the server still wrote to /var/lib/infosphere (from the old env value) while systemd only allowed /var/lib/knowforge, which is read-only under ProtectSystem=strict. Deploy now copies an existing /var/lib/infosphere into /var/lib/knowforge on first renamed release, and disables the old infosphere-* units to avoid port conflicts.	23 天前
knowforge.sudoers	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.	23 天前
new-version.sh	chore(release): promote unreleased changelog notes into new version	25 天前
nginx.conf.example	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.	23 天前
package-node-runtime.sh	feat(deploy): ship web runtime in single server binary	1 个月前
package-web-runtime.sh	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.	23 天前
release.sh	chore(deploy): commit the next version after a release	11 天前