Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docker-compose.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,17 @@ services:
- INBOUND_TLS=no # Don't require local clients to use TLS
- ACCEPTED_NETWORKS=172.16.0.0/12 # Only accept connections from docker's internal network

ropewiki_tileserver:
image: maptiler/tileserver-gl:latest
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we pin this more specifically? latest tags often break things on a schedule we don't control

restart: unless-stopped
ports:
- "8080:8080"
user: root
volumes:
- /mnt/rwimages/tiles:/data
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like a new requirement to have for a site deployment -- let's add documentation describing how someone would get the appropriate data since someone couldn't bring up a working site instance without it. These instructions should be complete and sufficient to bring up a deployment of the site, assuming the user has access to the right things (database backup, images folder)

command: -c config.json
depends_on: []

volumes:
ropewiki_database_storage:
name: ropewiki_database_storage
Expand Down
7 changes: 7 additions & 0 deletions reverse_proxy/services.conf
Original file line number Diff line number Diff line change
Expand Up @@ -76,3 +76,10 @@ server {
listen 80;
return 301 https://{{WG_HOSTNAME}}$request_uri;
}

server {
server_name tiles.{{WG_HOSTNAME}};
location / {
proxy_pass http://ropewiki_tileserver:8080;
}
}
Loading