Tileserver of basemap for applications.

• Maptiler/tileserver-gl docker
• OpenMapTiles Positron Style & Planning Positron Style
  • OpenMapTiles version is used in application
  • Planning version is kept for reference
• Nginx docker
• Certbot CLI
• Docker and Docker Compose
  • Native setup is possible for the tileserver and nginx. However, these instructions are for docker container setup.

The application is designed to serve mapbox vector tiles. The tiles are not tracked in source because they can be hundreds or thousands of megabytes each. (Depending on the source of the files, they may also be subject to licenses which restrict their distribution.) The application is configured to look for a generic "basemap.mbtiles" file. For general users, the mbtiles should be sourced, loaded into the tileserver folder, and renamed to basemap.mbtiles. For DCP uses, these data are stored in a private Digital Ocean space. As of 05 July 2023, the application uses northeast data from 2017.

The basemap.mbtiles file should be created before running the rest of the application.

For local development, the tiles may be served directly without relying on nginx. To start only the tileserver, run docker compose up tileserver. The tileserver will be available at localhost:8080.

For production and production-like environments, the tileserver should be served behind ngnix. To start both nginx and the tileserver, run docker compose up

Nginx will try to run on port 80 and 443. This is required for production configurations. However, it may cause issues during local development. Many systems prevent applications from running on these ports by default. This issue can be resolved by either:

1. Navigating to compose.yaml, changing 80:80 to 8000:80, and removing 443:443
   or
2. Exposing root privileged ports on the local machine

sudo setcap cap_net_bind_service=ep $(which rootlesskit)
systemctl --user restart docker

The basemap server works in tandem with labs-layers-api. The layers api contains references to the tile server which it then passes to its dependent applications. These references are in public/static/v3.json and data/base/style.json. For both of these references, https://tiles.planninglabs.nyc should be changed to the target url.

The Ngnix image is configured to use certbot for alpine linux. With the application running in docker on the production server, certification can be run with:

docker exec ${CONTAINER_ID} certbot -n -m ${CONTACT_EMAIL} -d ${DOMAINS} --nginx --agree-tos

Rebuilding the nginx container reset the changes certbot applied to default.conf on installation. However, the certifications will persist in the docker volumes. The certificates can be reinstalled with:

docker exec -it ${CONTAINER_ID} certbot -d ${DOMAINS} --nginx

(This command starts an interactive terminal for installation. When in doubt about the state of the certificates, this is the safest command to run)

Certificate renewal is achieved by placing a renewal script into the weekly periodic cronjob folder. However, the crond daemon needs to be started with each new container. It can be started with:

docker exec ${CONTAINER_ID} crond