Asian Men's Volleyball Challenge Cup
The Asian Men's Volleyball Challenge Cup is an international volleyball competition in Asia and Oceania contested by the bottom ten senior men's national teams of the members of Asian Volleyball Confederation (AVC), the sport's continent governing body. The tournaments have been awarded every two years since 2018.
Current season, competition or edition: | |
Sport | Volleyball |
---|---|
Founded | 2018 |
Inaugural season | 2018 |
No. of teams | 8 (Finals) |
Continent | Asia and Oceania (AVC) |
Most recent champion(s) | |
Most titles | |
TV partner(s) | SMMTV |
Official website | Asian Volleyball Confederation |
This event should not be confused with the other, more prestigious, continental competition for Asian national volleyball teams, the Asian Volleyball Championship and Asian Volleyball Cup.
Results summary
Year | Host | Final | Third place match | Teams | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Champions | Score | Runners-up | 3rd place | Score | 4th place | ||||||
2018 Details |
Colombo |
Iraq |
3–2 | Saudi Arabia |
Sri Lanka |
3–0 | Bangladesh |
8 | |||
2020 Details |
Cholpon-Ata |
Hosts
Times Hosted | Nations | Year(s) |
---|---|---|
1 | 2018 | |
1 | 2020 |
Participating nations
Nation | 2018 | Years |
---|---|---|
4th | 1 | |
6th | 1 | |
1st | 1 | |
7th | 1 | |
8th | 1 | |
2nd | 1 | |
3rd | 1 | |
5th | 1 | |
Total | 8 |
Debut of teams
Year | Debutants | Total |
---|---|---|
2018 | 8 | |
gollark: Well, what didn't work, then?
gollark: They aren't that hard. You just use `server_name` in the `server` block.
gollark: Not specifically wordpress, no.
gollark: I would probably use nginx, because I'm used to it and it has nicer configuration:```nginxhttp { # whatever important configuration you have for all HTTP servers, `nginx.conf` probably ships with some # fallback in case someone visits with an unrecognized Host header server { listen 80 default_server; listen [::]:80 default_server; return 301 http://somedomain$request_uri; } server { listen 80; # you may (probably do) want HTTPS instead, in which case this bit is somewhat different - you need to deal with certs and stuff, and use port 443 - also you should probably add HTTP/2 listen [::]:80; # IPv6 server_name domain1.com; location / { proxy_pass http://backend1:8080/; } } server { listen 80; listen [::]:80; server_name domain2.com; location / { proxy_pass http://backend2:8080/; } }}```
gollark: The reverse-proxy solution is in my opinion the best one, although it would require some config.
See also
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.