pitchfork proxy setup

• Usage: pitchfork proxy setup [FLAGS]
• Effect: modifies state

Configure local proxy DNS, HTTPS trust, and standard ports

Configure hostname resolution, HTTPS certificate trust, and access through port 443 (or 80 for HTTP). Prints a plan and asks for confirmation before applying changes. Use --dry-run to preview the plan without applying it.

The supervisor can run as your normal user. Setup uses sudo for system DNS files, Linux CA trust, and port redirects or Linux bind capabilities. On macOS, choose an unprivileged proxy.port, such as 8443, for the redirect. Linux can also grant permission to bind the default port, 443, directly.

With --pac, applications that honor proxy settings use pitchfork's proxy auto-config file instead of system DNS. This skips DNS changes and port redirects. Use an unprivileged listener port to avoid bind privileges; Linux still needs sudo for CA trust if the CA is not already trusted. macOS may request authorization for keychain or network settings changes.

Use --undo to reverse setup using its saved configuration records, even after proxy settings change. Files and proxy settings are checked for pitchfork ownership before removal.

Example:

pitchfork proxy setup --dry-run
pitchfork proxy setup
pitchfork proxy doctor
pitchfork proxy setup --undo

Flags

• --pac — Configure a proxy auto-config (PAC) file instead of the system resolver
• --undo — Remove recorded setup resources and restore saved proxy settings
• -y --yes — Apply without asking for confirmation
• --dry-run — Print the plan and exit without changing anything
• -h --help — Print help