|
You are here |
blog.ampli.fi | ||
| | | | |
jasonwilder.com
|
|
| | | | | [AI summary] This blog post discusses automating the configuration of an Nginx reverse proxy for Docker containers to simplify deployment and improve availability through dynamic templating and Docker APIs. | |
| | | | |
rohitgupta.xyz
|
|
| | | | | Increasing requests per second of an HTTP API being served with Nginx | |
| | | | |
joshuarogers.net
|
|
| | | | | Just over a year ago we went over how to setup a reverse proxy that would require our users to authenticate. In our original proxy article, we generated some NGinx configuration that looked a bit like... location / { proxy_pass http://jira; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } And it worked. And everyone was happy. Until the day the request came in that NGinx should add a fixed set of credentials to all upstream web requests. | |
| | | | |
thomas-leister.de
|
|
| | | Depending on the Cache retention, Mastodon uses ridiculous amounts of storage for its media files. Perfekt for cheap S3 storage. | ||