Нет описания

Thomas Dy aa492c6cf1 Update node server and frontend to use API v4 8 лет назад
lib aa492c6cf1 Update node server and frontend to use API v4 8 лет назад
rust-server c6109a561d Remove Transfer-Encoding headers when proxying 8 лет назад
.gitignore 493685e510 Initial commit 10 лет назад
README.md 26b4e18669 Update readme 8 лет назад
config.json.example ee6581f9c1 Make port configurable 8 лет назад
index.html 493685e510 Initial commit 10 лет назад
main.css 493685e510 Initial commit 10 лет назад
package.json fd82aa68b0 Force cortex version to 0.6.2 8 лет назад
server.js aa492c6cf1 Update node server and frontend to use API v4 8 лет назад
webpack.config.js 84a1b0cff5 Add woff2 in loader config 8 лет назад

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.