NUKE

test/nginx/conf/nginx/conf-nuke.inc

@@ -1,8 +1,8 @@
-# /etc/nginx/conf-anubis.inc
+# /etc/nginx/conf-nuke.inc
 
-# Forward to anubis
+# Forward to nuke
 location / {
   proxy_set_header Host $host;
   proxy_set_header X-Real-IP $remote_addr;
-  proxy_pass http://anubis;
-}
+  proxy_pass http://nuke;
+}

test/nginx/conf/nginx/conf.d/server-mimi-techaro-lol.conf

@@ -6,8 +6,8 @@ server {
   listen [::]:443 ssl;
   http2 on;
 
-  # Slipstream via Anubis
-  include "conf-anubis.inc";
+  # Slipstream via Nuke
+  include "conf-nuke.inc";
 
   server_name mimi.techaro.lol;
 
@@ -26,4 +26,4 @@ server {
 
   # Your normal configuration can go here
   # location .php { fastcgi...} etc.
-}
+}

test/nginx/conf/nginx/conf.d/upstream-nuke.conf

@@ -1,17 +1,17 @@
-# /etc/nginx/conf.d/upstream-anubis.conf
+# /etc/nginx/conf.d/upstream-nuke.conf
 
-upstream anubis {
-  zone anubis_zone 64k;
+upstream nuke {
+  zone nuke_zone 64k;
   # Make sure this matches the values you set for `BIND` and `BIND_NETWORK`.
-  # If this does not match, your services will not be protected by Anubis.
+  # If this does not match, your services will not be protected by Nuke.
 
-  # Try anubis first over a UNIX socket
-  #server unix:/run/anubis/nginx.sock;
-  server anubis:3000 resolve;
+  # Try nuke first over a UNIX socket
+  #server unix:/run/nuke/nginx.sock;
+  server nuke:3000 resolve;
 
   # Optional: fall back to serving the websites directly. This allows your
-  # websites to be resilient against Anubis failing, at the risk of exposing
+  # websites to be resilient against Nuke failing, at the risk of exposing
   # them to the raw internet without protection. This is a tradeoff and can
   # be worth it in some edge cases.
   #server unix:/run/nginx.sock backup;
-}
+}