| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
A REST API for LuckPerms.
The app can be configured using Java system properties or environment variables.
| Environment Variable | Description | Default Value |
|---|---|---|
| LUCKPERMS_REST_HTTP_PORT | The port that the HTTP server should listen on | 8080 |
| LUCKPERMS_REST_AUTH | If API key authorization is enabled | false |
| LUCKPERMS_REST_AUTH_KEYS | A comma-separated list of accepted API keys | none |
| LUCKPERMS_REST_CACHE_USERS | If the cache* should be used for user GET requests | true |
| LUCKPERMS_REST_CACHE_GROUPS | If the cache* should be used for group GET requests | true |
* When a messaging service is configured (recommended), the cache will be invalidated automatically whenever data is changed by other LP instances.
By default, the example Docker Compose setup only makes the API available to applications running on the host machine. For this reason, authentication is disabled by default.
However, if you decide to make the API available over a wider network (e.g. the internet), then it is crucial that you configure authentication using API keys and enable HTTPS by exposing the API behind a reverse proxy (e.g. nginx).
You enable auth by setting LUCKPERMS_REST_AUTH to true, and setting LUCKPERMS_REST_AUTH_KEYS to a comma separated list of allowed API keys.
e.g.
LUCKPERMS_REST_AUTH: "true"
LUCKPERMS_REST_AUTH_KEYS: "myverysecureapikey,anotherverysecurekey"Once enabled, API keys should be sent as a Bearer token inside the Authorization header of API requests. e.g.
Authorization: Bearer myverysecureapikey
| Back | FazBrowse Home | New Git URL |