dtoro
d4d99a7473
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.
44 lines
1.3 KiB
Markdown
44 lines
1.3 KiB
Markdown
http-proxy-agent
|
|
================
|
|
### An HTTP(s) proxy `http.Agent` implementation for HTTP
|
|
|
|
This module provides an `http.Agent` implementation that connects to a specified
|
|
HTTP or HTTPS proxy server, and can be used with the built-in `http` module.
|
|
|
|
__Note:__ For HTTP proxy usage with the `https` module, check out
|
|
[`https-proxy-agent`](../https-proxy-agent).
|
|
|
|
|
|
Example
|
|
-------
|
|
|
|
```ts
|
|
import * as http from 'http';
|
|
import { HttpProxyAgent } from 'http-proxy-agent';
|
|
|
|
const agent = new HttpProxyAgent('http://168.63.76.32:3128');
|
|
|
|
http.get('http://nodejs.org/api/', { agent }, (res) => {
|
|
console.log('"response" event!', res.headers);
|
|
res.pipe(process.stdout);
|
|
});
|
|
```
|
|
|
|
API
|
|
---
|
|
|
|
### new HttpProxyAgent(proxy: string | URL, options?: HttpProxyAgentOptions)
|
|
|
|
The `HttpProxyAgent` class implements an `http.Agent` subclass that connects
|
|
to the specified "HTTP(s) proxy server" in order to proxy HTTP requests.
|
|
|
|
The `proxy` argument is the URL for the proxy server.
|
|
|
|
The `options` argument accepts the usual `http.Agent` constructor options, and
|
|
some additional properties:
|
|
|
|
* `headers` - Object containing additional headers to send to the proxy server
|
|
in each request. This may also be a function that returns a headers object.
|
|
|
|
**NOTE:** If your proxy does not strip these headers from the request, they
|
|
will also be sent to the destination server. |