npm Registry Caching Proxy 4 Replies Prevent your continuous integration/deployment workflow from pummeling the npm registry’s couchdb. Reduce headaches and errors during npm install. user www-data; worker_processes 4; error_log /var/log/nginx/error.log; pid /var/run/nginx.pid; events { worker_connections 1024; } http { include /etc/nginx/mime.types; access_log off; default_type application/octet-stream; sendfile on; tcp_nodelay on; tcp_nopush off; reset_timedout_connection on; server_tokens off; # Cache 10G worth of packages for up to 1 month proxy_cache_path /var/lib/nginx/npm levels=1:2 keys_zone=npm:16m inactive=1M max_size=10G; # Multiple server definitions makes nginx retry upstream registry_npm { server registry.npmjs.org; server registry.npmjs.org; keepalive 16; } gzip on; gzip_types application/json text/css text/javascript; gzip_proxied any; gzip_vary on; server { listen 80 default_server; server_name npm.example.com; root /var/www; proxy_cache npm; proxy_cache_key $uri; proxy_cache_lock on; proxy_cache_use_stale error timeout updating http_500 http_502 http_503 http_504; proxy_http_version 1.1; proxy_pass_request_headers off; proxy_set_header Host registry.npmjs.org; location / { proxy_cache_valid any 5m; add_header X-Cache $upstream_cache_status; proxy_pass http://registry_npm; } location ~ ^/.+/-/.+ { proxy_cache_valid any 1M; add_header X-Cache $upstream_cache_status; proxy_pass http://registry_npm; } } } Be Sociable, Share! Tweet
