Overview / Migration
Using another proxy?
Use the Thwip migration skill to turn supported proxy configuration into a candidate TOML file, while preserving a clear list of behavior that needs manual work or is not supported yet.
Configuration migration skill
Give the skill an Nginx, Caddy, HAProxy, or similar proxy configuration. It maps straightforward listeners, host names, exact/prefix routes, static roots, direct HTTP upstreams, and weighted upstream groups into Thwip configuration.
It does not guess at missing equivalents. The result always separates the candidate configuration from the decisions that still need attention.
Migration warnings
The skill can map basic TLS termination when one certificate is sufficient, but calls out SNI certificate selection and HTTPS upstreams as unsupported. It also flags regex routes, rewrites, PHP/FastCGI, WebSockets, UDP, advanced load balancing, retries, health checks, header rules, caching, compression, rate limits, and keep-alive- or chunked-body-dependent behavior.
For each warning it states whether you should preserve the existing proxy in front of Thwip, simplify the configuration, or wait for a roadmap feature. A partially migrated file is never presented as an equivalent replacement.