Differences

This shows you the differences between two versions of the page.

--- nginxarchitecture [2024/10/27 01:59] – [PHP-FPM Config and Optimize] admin
+++ nginxarchitecture [2024/10/27 02:55] (current) – [Basic Nginx Configuration] admin
@@ Line 26: / Line 26: @@
   * Since Nginx comes only with core features that are required for a web server, **it is lightweight when compared to Apache**.
   * The performance and scalability of Nginx is not completely dependent on hardware resources, whereas the performance and scalability of the Apache is dependent on underlying hardware resources like memory and CPU.
+===== Basic Nginx Configuration =====
+Some basic directives:
+  * Location (refer: https://docs.nginx.com/nginx/admin-guide/basic-functionality/managing-configuration-files/)<code ini>
+user nobody; # a directive in the 'main' context
+events {
+    # configuration of connection processing
+}
+http {
+    # Configuration specific to HTTP and affecting all virtual servers
+    server {
+        # configuration of HTTP virtual server 1
+        location /one {
+            # configuration for processing URIs starting with '/one'
+        }
+        location /two {
+            # configuration for processing URIs starting with '/two'
+        }
+    }
+    server {
+        # configuration of HTTP virtual server 2
+    }
+}
+stream {
+    # Configuration specific to TCP/UDP and affecting all virtual servers
+    server {
+        # configuration of TCP virtual server 1
+    }
+}
+</code>
+  * request_filename (refer: https://docs.nginx.com/nginx/admin-guide/web-server/web-server/)<code>
+if (!-e $request_filename) { rewrite ^ /path/index.php last; }
+</code> => This checks whether there is a file, directory, or symbolic link that **matches the $request_filename**. If such a file is **not found**, the connection is being **redirected to /path/index.php**.
+  * try_files (refer https://docs.nginx.com/nginx/admin-guide/web-server/serving-static-content/)<code>
+location / {
+    try_files $uri $uri/ $uri.html =404;
+}
+</code><code>
+location / {
+    try_files $uri $uri/ /test/index.html;
+}
+</code> => you probably understand:<code>
+location / => matches all locations**
+try_files $uri =>try $uri first, for example http://example.com/images/image.jpg nginx will try to check if there's a file inside /images called image.jpg if found it will serve it first.
+$uri/=> which means if you didn't find the first condition $uri try the URI as a directory
+</code>
 ===== Optimize nginx configuration for performance and benchmark =====
 refer: