Thomas Dy
448c9e0ea6
Forward headers when proxying zone_load_multi
|
8 years ago | |
|---|---|---|
| lib | 9 years ago | |
| rust-server | 8 years ago | |
| .gitignore | 10 years ago | |
| README.md | 8 years ago | |
| config.json.example | 8 years ago | |
| index.html | 10 years ago | |
| main.css | 10 years ago | |
| package.json | 8 years ago | |
| server.js | 10 years ago | |
| webpack.config.js | 8 years ago |
README.md
Cloudflare WebUI
This is a web frontend to the Cloudflare API. It mainly lets you manage DNS records, but it also lets you toggle development mode and purge the cache.
This was mainly built to work around Cloudflare only having multi-user support for enterprise. It's a simple frontend for the DNS settings and a simple webserver that handles making the actual requests to Cloudflare.
Usage
Download the binary (only Linux x86_64 for now). Get a copy of
config.json.example and name it config.json. Place it in the same directory
as the binary. Fill in your account details and the domains to be whitelisted.
Afterwards, run the binary and you should be able to manage your domains at
localhost:8000.
Security
The server only listens at 127.0.0.1. It does not provide any form of authentication. It is meant to be run behind a reverse proxy such as nginx with basic auth, or behind something like oauth2_proxy.
The server never exposes your username and token to the clients, all requests to Cloudflare are made from the server. The server will also only allow API requests to domains specified in the whitelist. Domains not listed will be blocked even if your account owns it.