chore(vnc): bootstrap VNCmail+ fork — vnc/ layer + Vercel runbook
Fork of bulwarkmail/webmail for deploy on Vercel as project vncmail-plus. Adds vnc/ customization layer (branding, overrides, VNC-CHANGES log), Vercel env template, and VNCMAIL-SETUP.md runbook. No upstream files touched. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
e94a1429d5
commit
eace443fdf
@@ -0,0 +1,26 @@
|
||||
# VNC-CHANGES — VNCmail+ divergence log
|
||||
|
||||
VNCmail+ is a fork of [bulwarkmail/webmail](https://github.com/bulwarkmail/webmail)
|
||||
(AGPL-3.0). This file records **every** intentional divergence from upstream so
|
||||
that merging new upstream releases stays a triage exercise, not an archaeology dig.
|
||||
|
||||
## Rules of the fork
|
||||
|
||||
1. **Keep upstream files unmodified whenever possible.** Prefer env vars
|
||||
(branding), the `vnc/overrides/` layer, and additive files over editing files
|
||||
inside `app/`, `components/`, `lib/`, `stores/`.
|
||||
2. **Every edit to an upstream file gets a one-line entry below** — path, what,
|
||||
why. No silent edits.
|
||||
3. **Branches:** `main` tracks upstream releases (kept clean); `dev` is the VNC
|
||||
integration + Vercel deploy branch; `vnc/*` are feature branches.
|
||||
4. **Syncing upstream:** `git fetch upstream && git merge upstream/main` onto
|
||||
`main`, then merge `main` into `dev`. Resolve using this log.
|
||||
|
||||
## Divergences
|
||||
|
||||
| Date | File / area | Change | Why |
|
||||
|------|-------------|--------|-----|
|
||||
| 2026-08-03 | `vnc/` (new) | Added VNC customization dir + this log | Fork bootstrap |
|
||||
| 2026-08-03 | `VNCMAIL-SETUP.md` (new) | Vercel deploy runbook | Deploy on Vercel as project "VNCmail+" |
|
||||
|
||||
_(append new rows as you diverge)_
|
||||
Reference in New Issue
Block a user