GreenFrame provides an HTTP Tunneling server based on FRP, to let you expose private websites to the analyzer. With this method, you can use GreenFrame to analyze applications running locally, in a private staging server, or in your CI.
This method is useful only if you use --distant flag to run your analysis on GreenFrame server
The FRP client installation process depends on your OS and bash. To simplify it, GreenFrame exposes a shell script that reduces the installation to a one-liner:
curl https://assets.greenframe.io/install-frpc.sh | bash
If the installation works well, you can type
frpc -v to see the version.
You can also find all releases of the FRP client in the FRP GitHub Releases page.
In your project, add a file named
frpc.ini with the following content:
custom_domains must be unique, because if they are already took by someone else, you won't be able to run analysis every time.
You can for example use an uuid generator to generate an unique identifier and create your own unique domain:
Then run the FRP client in the folder containing the
Your app should be available at the following url:
Please note the :8080 port at the end.
Your app may expose more than one server, for instance your app is a Single-Page Application using an API.
If you setup tunneling only for the frontend, the app won't be able to communicate with the API exposed on
In this case, you have to tunnel both the frontend and the API, and tell the frontend to use the proxied API URL.
With this configuration, you have to set the API URL your frontnd app should use, for instance by using an environment variable:
To be documented