Commit Graph
5 Commits
Author SHA1 Message Date
jcoffey-dev 92bcb58f76 AGPL source offer, notices and name cleanup
Every build writes the exact tree it was built from, uncommitted work
included, as source.tar.gz next to the app, and names that tree. The sidebar,
user menu, sign-in card and version tooltip link to it.

Coffey Labs' copyright line is added below Stalwart Labs' in every inherited
file changed, and the new files carry Coffey Labs' alone.

The upgrade prompt and its links are gone, the edition tooltip is neutral,
storage keys and the package description are INBUXA's own, and the README
states the lineage once, in the fine print.
2026-09-19 00:01:57 -07:00
jcoffey-dev 14d708ecf8 Go straight to the server's sign-in page, with no account-name step
INBUXA Admin talks to one known server whose own page signs in every account,
so it reads the server's OpenID configuration instead of looking endpoints up
per account. The login card now only shows while redirecting, or to retry
when that fails.
2026-09-18 15:50:10 -07:00
jcoffey-dev 2399f5ce97 Sign in as inbuxa-admin when hosted apart from the server (inbuxa-server contract C-6) 2026-09-18 13:05:04 -07:00
jcoffey-dev e387e7976f Versioning: INBUXA Admin's own dated version, with the WebUI base shown
inbuxa-version.json holds INBUXA's version. package.json keeps upstream's so
its bumps merge cleanly. The top bar reads "INBUXA Admin 2026.9.18 (WebUI 1.0.11)".
2026-09-18 12:09:52 -07:00
jcoffey-dev 1d72ef3aa1 Fork Stalwart WebUI v1.0.11 as INBUXA Admin
- One edition: whatever edition the server reports, nothing is hidden or
  disabled as Enterprise-only (accountStore.setAccountInfo).
- INBUXA branding: name, logo (mark plus a text-colored wordmark), favicon,
  page titles, setup wizard text, and ihasmail's palette in light and dark.
- Two-factor setup names INBUXA as the issuer and drops the image parameter
  that made authenticator apps fetch a logo from a third-party site.
- Runs apart from the server: the server address can be set at deploy time
  with <meta name="api-base-url">, and OAuth endpoints the server returns as
  relative paths are resolved against the server's address, not the page's.
  Verified end to end against a separate inbuxa-server.
- Upstream's release workflow moved to .github-upstream so it never runs.

Upstream's history contains no Enterprise-only code, so this is an ordinary
fork. upstream is a fetch-only remote.
2026-09-18 12:00:54 -07:00