Differences

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

--- marfeel:test [2020/03/16 12:11] – created dodger
+++ marfeel:test [2020/10/23 09:50] (current) – removed dodger
@@ Line 1: / Line 1: @@
-====== Marfeel Test ======
-====== App server ======
-===== Why do you think different cache times for the nginx cache and for the browser were defined? =====
-General answer: Caching is mandatory for performance.
-  * Particular answer to proxy cache:
-    * I've configured nginx proxy_cache on /dev/shm for performance (on ram cache). 1 minute for proxy_cache should be fine if the content is changing constantly, cause nginx will "rebuild/compile" the cache after 1 minute but inside that minute, it will use the already compiled version of the file.
-  * Particular answer to static content:
-    * Static content to 1 hour maybe is aggressive, normally I set it up to 1day or more, also depends on the type of application.
-  * Particular answer to proxied content:
-    * I Think we must include a header like "If-Modified-Since" to invalidate local cache if the file has been changed on the server.
-====== Auto-scaling ======
-===== Ami and UserData =====
-I did some mistakes, so I create some versions of it:
-  * name : dodger_marfeel_test_003
-  * id : ami-0bc1be25784321fc1
-===== Which code have you added to the user-data on launching the instance? =====
-<code yaml>
-#cloud-config
-runcmd:
-  - [ mkdir, -p, /opt/test ]
-  - [ wget, -O/opt/test/master.tar.gz, "https://bitbucket.org/Marfeel/appserverpythontestapp/get/master.tar.gz" ]
-  - [ tar, xzfv, /opt/test/master.tar.gz, -C, /opt/test/ ]
-  - [ systemctl, start, marfeel_test ]
-  - [ systemctl, restart, nginx ]
-</code>
-===== Security group =====
-I create the 001 group with https, then I remove it in the 2nd version:
-  * name: dodger_launch_002
-===== auto-scaling Group =====