feat: Phase 1 — extract the client (web SPA + desktop) to dtoro/oikos-web
Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
This commit is contained in:
33
web/node_modules/tough-cookie/dist/cookie/canonicalDomain.d.ts
generated
vendored
Normal file
33
web/node_modules/tough-cookie/dist/cookie/canonicalDomain.d.ts
generated
vendored
Normal file
@@ -0,0 +1,33 @@
|
||||
import type { Nullable } from '../utils';
|
||||
/**
|
||||
* Transforms a domain name into a canonical domain name. The canonical domain name is a domain name
|
||||
* that has been trimmed, lowercased, stripped of leading dot, and optionally punycode-encoded
|
||||
* ({@link https://www.rfc-editor.org/rfc/rfc6265.html#section-5.1.2 | Section 5.1.2 of RFC 6265}). For
|
||||
* the most part, this function is idempotent (calling the function with the output from a previous call
|
||||
* returns the same output).
|
||||
*
|
||||
* @remarks
|
||||
* A canonicalized host name is the string generated by the following
|
||||
* algorithm:
|
||||
*
|
||||
* 1. Convert the host name to a sequence of individual domain name
|
||||
* labels.
|
||||
*
|
||||
* 2. Convert each label that is not a Non-Reserved LDH (NR-LDH) label,
|
||||
* to an A-label (see Section 2.3.2.1 of [RFC5890] for the former
|
||||
* and latter), or to a "punycode label" (a label resulting from the
|
||||
* "ToASCII" conversion in Section 4 of [RFC3490]), as appropriate
|
||||
* (see Section 6.3 of this specification).
|
||||
*
|
||||
* 3. Concatenate the resulting labels, separated by a %x2E (".")
|
||||
* character.
|
||||
*
|
||||
* @example
|
||||
* ```
|
||||
* canonicalDomain('.EXAMPLE.com') === 'example.com'
|
||||
* ```
|
||||
*
|
||||
* @param domainName - the domain name to generate the canonical domain from
|
||||
* @public
|
||||
*/
|
||||
export declare function canonicalDomain(domainName: Nullable<string>): string | undefined;
|
||||
Reference in New Issue
Block a user