<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Couchdb on Lloyd Rochester's Geek Blog</title><link>https://lloydroc.github.io/tags/couchdb/</link><description>Recent content in Couchdb on Lloyd Rochester's Geek Blog</description><generator>Hugo</generator><language>en</language><copyright>Copyright © 2025, Lloyd Rochester.</copyright><lastBuildDate>Wed, 10 Oct 2018 03:10:00 +0000</lastBuildDate><atom:link href="https://lloydroc.github.io/tags/couchdb/index.xml" rel="self" type="application/rss+xml"/><item><title>NGINX/CouchDB Reverse Proxy</title><link>https://lloydroc.github.io/post/networking/couchdb-nginx-proxy/</link><pubDate>Wed, 10 Oct 2018 03:10:00 +0000</pubDate><guid>https://lloydroc.github.io/post/networking/couchdb-nginx-proxy/</guid><description>&lt;p>Using NGINX as a front-end server to forward to multiple back-end services works great by configuring NGINX as a reverse proxy. The reverse proxy configuration will have NGINX serve HTTP/HTTPS URLs and forward them to them to network addresses such as a database listening on HTTP at a specific port, API servers, static websites, etc. Basically we can turn NGINX into an HTTP router. NGINX is also a great front man for back-end services such as HTTPS and HTTP/2. For instance if you had a Database, API Server and static site you could have an SSL certificate just for NGINX and they would all be behind HTTPS and the reverse proxy would convert the HTTPS and send HTTP. That&amp;rsquo;s a post for another time however.&lt;/p></description></item></channel></rss>