| #user nobody; | |
| worker_processes 4; | |
| #error_log logs/error.log; | |
| #error_log logs/error.log notice; | |
| #error_log logs/error.log info; | |
| #pid logs/nginx.pid; |
DNS queries on home network suddenly resolving hosts to 104.239.207.44.
You will see SPORADIC mis-resolutions of EVERYTHING to that 104.239.207.44 address if their crappy router happens to hear your PC's DHCP request - EVEN IF ANOTHER DHCP SERVER ON THE NETWORK assigns the ultimate address.
nginx uses a fixed number of workers, each of which handles incoming requests. The general rule of thumb is that you should have one worker for each CPU-core your server contains.
You can count the CPUs available to your system by running:
$ grep ^processor /proc/cpuinfo | wc -l
overwatch is 16MF9 while source is 4ML3, search these terms in this discord for some definitions for them. let us arbitrarily set your screen resolution to w x h for width/height.
note. i call fortnite 80hML in the examples below; this is not exactly true, fortnite is 16MI9, see this document for more information about FILM notation
the key idea here is to match focal length between games (or more precisely FoVs), which is the normal distance from the camera (you) to the canvas upon which the game is drawn. matching this length causes objects moving at the same velocities in both FoVs to have the same motion on your screen, which is arguably the most important part of aiming.
how do we calculate focal length? if we know how our game scales its implicit image, and its nominal FoV, then we can compute the focal length with some geometry/trig. you are one question or google search away from figuring out your n
| # Bazarr downloads subtitles | |
| version: "3.4" | |
| services: | |
| bazarr: | |
| image: linuxserver/bazarr:1.0.5-development | |
| container_name: bazarr | |
| restart: unless-stopped | |
| environment: | |
| - TZ=Europe/London |