Gmina Czyże

Gmina Czyże is a rural gmina (administrative district) in Hajnówka County, Podlaskie Voivodeship, in north-eastern Poland. Its seat is the village of Czyże, which lies approximately 12 kilometres (7 mi) north-west of Hajnówka and 41 km (25 mi) south-east of the regional capital Białystok.

Gmina Czyże

Czyże Commune
Gmina
Coat of arms
Coordinates (Czyże): 52°47′N 23°25′E
Country Poland
VoivodeshipPodlaskie
CountyHajnówka
SeatCzyże
Government
 • MayorJerzy Wasiluk
Area
 • Total134.2 km2 (51.8 sq mi)
Population
 (2006)
 • Total2,528
 • Density19/km2 (49/sq mi)
Websitehttp://www.ugczyze.pl/

The gmina covers an area of 134.2 square kilometres (51.8 sq mi), and as of 2006 its total population is 2,528.

It is one of five Polish/Belarusian bilingual Gmina in Podlaskie Voivodeship regulated by the Act of 6 January 2005 on National and Ethnic Minorities and on the Regional Languages, which permits certain gminas with significant linguistic minorities to introduce a second, auxiliary language to be used in official contexts alongside Polish.[1]

Villages

Gmina Czyże contains the villages and settlements of Bujakowszczyzna, Czyże, Hrabniak, Hukowicze, Kamień, Klejniki, Kojły, Kuraszewo, Lady, Leniewo, Leszczyny, Łuszcze, Maksymowszczyzna, Morze, Osówka, Podrzeczany, Podwieżanka, Rakowicze, Sapowo, Szostakowo, Wieżanka, Wólka and Zbucz.

Neighbouring gminas

Gmina Czyże is bordered by the gminas of Bielsk Podlaski, Dubicze Cerkiewne, Hajnówka, Narew and Orla.

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.
gollark: Yes, and you can just use a reverse proxy (with "vhosts" or whatever) for that, easy enough.
gollark: I think those are just what some webservers call "doing different things based on the host header".

References
  1. Dz. U. z 2005 r. Nr 17, poz. 141
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.