Minor fix and move URLs to .app

This commit is contained in:
Ian Renton
2025-10-07 16:20:03 +01:00
parent 2dcfae98f8
commit abff65f78d
5 changed files with 12 additions and 12 deletions

View File

@@ -16,7 +16,7 @@ Supported data sources include DX Clusters, the Reverse Beacon Network (RBN), th
### Accessing the public version
You can access the public version's web interface at [https://spothole.m0trt.radio](https://spothole.m0trt.radio), and see [https://spothole.m0trt.radio/apidocs](https://spothole.m0trt.radio/apidocs) for the API details.
You can access the public version's web interface at [https://spothole.app](https://spothole.app), and see [https://spothole.app/apidocs](https://spothole.app/apidocs) for the API details.
Please note this URL is not necessarily final, and the API is likely to change as the project works its way towards v1.0. Please do not build anything on the Spothole API yet!
@@ -81,7 +81,7 @@ Check the service has started up correctly with `sudo journalctl -u spothole -f`
It's best not to serve Spothole directly on port 80, as that requires root privileges and prevents us using HTTPS, amongst other reasons. To set up nginx as a reverse proxy that sits in front of Spothole, first ensure it's installed e.g. `sudo apt install nginx`, and enabled e.g. `sudo systemd enable nginx`.
Create a file at `/etc/nginx/sites-available/` called `spothole`. Give it the following contents, replacing `spothole.m0trt.radio` with the domain name on which you want to run Spothole. If you changed the port on which Spothole runs, update that on the "proxy_pass" line too.
Create a file at `/etc/nginx/sites-available/` called `spothole`. Give it the following contents, replacing `spothole.app` with the domain name on which you want to run Spothole. If you changed the port on which Spothole runs, update that on the "proxy_pass" line too.
```nginx
map $request_uri $xssorigin {
@@ -89,7 +89,7 @@ map $request_uri $xssorigin {
}
server {
server_name spothole.m0trt.radio;
server_name spothole.app;
# Wellknown area for Lets Encrypt
location /.well-known/ {