CD Pozoblanco

Club Deportivo Pozoblanco is a Spanish football team based in Pozoblanco, Córdoba, in the autonomous community of Andalusia. Founded in 1926, it plays in Tercera División – Group 10, holding home matches at Estadio Municipal Pozoblanco, with a 4,000-seat capacity.

Pozoblanco
Full nameClub Deportivo Pozoblanco
Founded1926
GroundMunicipal, Pozoblanco,
Andalusia, Spain
Capacity4,000
President José Antonio Bravo
Head coach Mario Rojas
League3ª – Group 10
2011–123ª – Group 10, 12th

Season to season

Season Tier Division Place Copa del Rey
1956/57 3 11th
1957/58 3 17th
1958/59 4 Regional
1959/60 3 15th
1960–80 5 Regional
1980/81 4 6th
1981/82 4 16th
1982/83 4 4th
1983/84 4 9th
1984/85 4 6th
1985/86 4 5th
1986/87 4 18th
1987/88 5 Regional
1988/89 5 Regional
1989/90 4 5th
1990/91 4 5th
1991/92 4 7th
1992/93 4 10th
1993/94 4 18th
Season Tier Division Place Copa del Rey
1994/95 4 1st
1995/96 4 8th
1996/97 4 9th
1997/98 4 16th
1998/99 4 12th
1999/00 4 7th
2000/01 4 11th
2001/02 4 17th
2002/03 5 Reg. Pref. 2nd
2003/04 5 Reg. Pref. 1st
2004/05 4 6th
2004/05 4 17th
2006/07 4 12th
2007/08 4 5th
2008/09 4 10th
2009/10 4 6th
2010/11 4 3rd
2011/12 4 12th
2012/13 4

Former players

Former coaches

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.
gollark: I think LetsEncrypt may not be very happy with that, though.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.