Running¶
There are several ways to run Burp-UI. You can either use the embedded Flask’s development server or you can use any of the deployement options provided by Flask.
Note
I personally focus on gunicorn
support for production deployments
Sandboxing¶
If you want to play with Burp-UI to PoC it or if you are going to be the only user, you can absolutely use the embedded server. If you plan to run Burp-UI in production, then you should go with Gunicorn.
Option 1¶
You can run the embedded server with the following command:
burp-ui
By default, the server listens on localhost:5000. You can easily change this
by adding the -- -h x.x.x.x -p yyyy
options. See here
for details.
Option 2¶
Prior to v0.4.0, you could specify the bind and port option within the Burp-UI configuration file. You can still use this behavior by running:
python -m burpui -m legacy [--help]
Note
Since v0.5.0, you can also use the burp-ui-legacy
command to
achieve the same thing.
Production¶
Like I said earlier, I recommend using Gunicorn for production deployments. You can refer to the dedicated gunicorn page of this documentation to know everything on how to Burp-UI through Gunicorn.
Going further¶
Please refer to the advanced usage page for details on how to use/customize Burp-UI.