Version info below.
Sticking very close to the sample files in
https://github.com/reviewboard/reviewboard/tree/master/contrib/docker/examples/... when I ran:
docker-compose -f docker-compose.mysql.yaml -p reviewboard_mysql up
I got...
service "reviewboard" refers to undefined volume sitedir: invalid compose project
If I added the following lines to the yaml file...
volumes:
db_data:
sitedir:
... it then appeared to work as might be expected.
The nginx part (about which I know little) is not happy. The only response I ever get from visiting
http://welty.verilab.com/ is: "Bad Request (400)"
I'm pretty sure the nginx template file (shown below) *is* being read,
but nothing ever gets proxy'd back to the reviewboard server. I have
few ideas about what to poke to find out what it is not happy about. I
welcome any input. Thanks,
Will
=== version info
Linux
veri-dock1.verilab.com 4.19.0-23-amd64 #1 SMP Debian 4.19.269-1 (2022-12-20) x86_64 GNU/Linux (i.e. Debian 10)
$ docker --version
Docker version 23.0.1, build a5ee5b1
$ docker-compose --version
Docker Compose version v2.16.0
=== nginx file
upstream reviewboard {
server reviewboard:8080;
}
server {
server_name
welty.verilab.com;
listen 80;
root /var/www/reviewboard/htdocs;
location / {
proxy_pass
http://reviewboard;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header Host $host;
proxy_redirect off;
}
location /media/ {
alias /var/www/reviewboard/htdocs/me
dia/;
add_header Access-Control-Allow-Origin *;
expires max;
location ~ \.(html|htm|shtml|php)$ {
types {}
default_type text/plain;
}
}
location /static/ {
alias /var/www/reviewboard/htdocs/st
atic/;
add_header Access-Control-Allow-Origin *;
expires max;
}
location /errordocs/ {
alias /var/www/reviewboard/htdocs/er
rordocs/;
expires 30d;
}
}