Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.rockxy.io/llms.txt

Use this file to discover all available pages before exploring further.

​
Terminal Runtimes and Frameworks

Local runtimes and framework toolchains are some of the most valuable Rockxy targets, but they are also the least likely to “just work” with the macOS system proxy alone.

​
Why this category needs special handling

Many command-line tools and dev runtimes need explicit:
  • proxy environment variables,
  • runtime-specific proxy support,
  • or extra certificate trust configuration.

​
Runtime guides

Rockxy currently ships separate target pages for: Framework and environment targets that still live near this workflow:
  1. choose the exact runtime or framework in Developer Setup Hub,
  2. use the generated snippet or guide for that target,
  3. run the validation request first,
  4. only then run the real app or script.

​
Common failure pattern

The runtime sends nothing to Rockxy because:
  • the process ignores the system proxy,
  • the environment variables were not applied to the actual process,
  • or the runtime rejected the local certificate.

Frameworks

Use the dedicated framework hub for Flutter, React Native, Next.js, and ElectronJS.

Environments

Jump to Docker and other environment-oriented setup paths.

API Debugging on macOS

See how these runtime flows fit into a practical API debugging workflow.

Capture Issues

Continue here if the runtime still does not emit visible traffic.