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.
47 lines
2.0 KiB
TypeScript
47 lines
2.0 KiB
TypeScript
/// <reference types="node" />
|
|
/// <reference types="node" />
|
|
/// <reference types="node" />
|
|
/// <reference types="node" />
|
|
import * as net from 'net';
|
|
import * as tls from 'tls';
|
|
import * as http from 'http';
|
|
import { Agent, AgentConnectOpts } from 'agent-base';
|
|
import { URL } from 'url';
|
|
import type { OutgoingHttpHeaders } from 'http';
|
|
type Protocol<T> = T extends `${infer Protocol}:${infer _}` ? Protocol : never;
|
|
type ConnectOptsMap = {
|
|
http: Omit<net.TcpNetConnectOpts, 'host' | 'port'>;
|
|
https: Omit<tls.ConnectionOptions, 'host' | 'port'>;
|
|
};
|
|
type ConnectOpts<T> = {
|
|
[P in keyof ConnectOptsMap]: Protocol<T> extends P ? ConnectOptsMap[P] : never;
|
|
}[keyof ConnectOptsMap];
|
|
export type HttpsProxyAgentOptions<T> = ConnectOpts<T> & http.AgentOptions & {
|
|
headers?: OutgoingHttpHeaders | (() => OutgoingHttpHeaders);
|
|
};
|
|
/**
|
|
* The `HttpsProxyAgent` implements an HTTP Agent subclass that connects to
|
|
* the specified "HTTP(s) proxy server" in order to proxy HTTPS requests.
|
|
*
|
|
* Outgoing HTTP requests are first tunneled through the proxy server using the
|
|
* `CONNECT` HTTP request method to establish a connection to the proxy server,
|
|
* and then the proxy server connects to the destination target and issues the
|
|
* HTTP request from the proxy server.
|
|
*
|
|
* `https:` requests have their socket connection upgraded to TLS once
|
|
* the connection to the proxy server has been established.
|
|
*/
|
|
export declare class HttpsProxyAgent<Uri extends string> extends Agent {
|
|
static protocols: readonly ["http", "https"];
|
|
readonly proxy: URL;
|
|
proxyHeaders: OutgoingHttpHeaders | (() => OutgoingHttpHeaders);
|
|
connectOpts: net.TcpNetConnectOpts & tls.ConnectionOptions;
|
|
constructor(proxy: Uri | URL, opts?: HttpsProxyAgentOptions<Uri>);
|
|
/**
|
|
* Called when the node-core HTTP client library is creating a
|
|
* new HTTP request.
|
|
*/
|
|
connect(req: http.ClientRequest, opts: AgentConnectOpts): Promise<net.Socket>;
|
|
}
|
|
export {};
|
|
//# sourceMappingURL=index.d.ts.map
|