chore: use latest stable nixpkgs globally

.gitignore

@@ -12,3 +12,4 @@ nix/nginx/logs/nginx.pid
 *.bc
 *.control
 *.so
+nginx.pid

docs/contributing.md

@@ -56,86 +56,6 @@ select net.http_get('http://localhost:3000/projects');
 -- * Connection #0 to host localhost left intact
 ```
 
-### Reproducible setup for load testing
-
-This will deploy a client and server on t3a.nano. You must have `supabase-dev` setup in `.aws/credentials`.
-
-```bash
-nixops create nix/deploy.nix -d pg_net
-
-nixops deploy -d pg_net
-# will take a while
-```
-
-Then you can connect on the client instance and do requests to the server instance through `pg_net`.
-
-```bash
-nixops ssh -d pg_net client
-
-psql -U postgres
-
-create extension pg_net;
-
-select net.http_get('http://server');
-# this the default welcome page of nginx on the server instance
-# "server" is already included to /etc/hosts, so `curl http://server` will give the same result
-
-# do some load testing
-select net.http_get('http://server') from generate_series(1,1000);
-# run `top` on another shell(another `nixops ssh -d pg_net client`) to check the worker behavior
-```
-
-#### Testing a slow response
-
-Locally:
-
-```bash
-net-with-pg-12 psql
-
-# takes some seconds to respond
-select net.http_get('http://localhost:8080/slow-reply');
-```
-
-With the cloud NixOps setup:
-
-```bash
-nixops ssh -d pg_net client
-
-# takes some seconds to respond
-select net.http_get('http://server/slow-reply');
-```
-
-#### Destroying the setup
-
-To destroy the instances:
-
-```bash
-nixops destroy -d pg_net --confirm
-nixops delete -d pg_net
-```
-
-### Run Valgrind to check memory leaks
-
-Start a postgres instance under valgrind.
-
-```
-valgrind-net-with-pg-12
-
-# it should show this output:
-# Connect to this db from another shell using the following command:
-#
-#        psql -h <path> -U postgres
-
-# connect to the db in another shell
-psql -h <path> -U postgres
-
-create extension pg_net;
-select net.http_get('https://supabase.io');
-
-# stop the db instance
-# then see the valgrind results in "valgrindlog"
-```
-
 ## Documentation
 
 All public API must be documented. Building documentation requires python 3.6+

nix/nginx/conf/nginx.conf

@@ -1,5 +1,5 @@
 daemon off;
-error_log /dev/stdout info;
+pid        ./nginx.pid;
 
 events {}
 

nix/nginxScript.nix

@@ -1,14 +1,19 @@
-{ openresty, writeShellScriptBin } :
+{ nginx, nginxModules, writeShellScriptBin } :
 
 let
+  customNginx = nginx.override {
+    modules = [
+      nginxModules.echo
+    ];
+  };
   script = ''
     set -euo pipefail
 
-    export PATH=${openresty}/bin:"$PATH"
+    export PATH=${customNginx}/bin:"$PATH"
 
-    trap 'killall openresty' sigint sigterm exit
+    trap 'killall nginx' sigint sigterm exit
 
-    openresty -p nix/nginx &
+    nginx -p nix/nginx -e stderr &
 
     "$@"
   '';