<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Reverse-Proxy on dev.endevour</title><link>https://devendevour.iankulin.com/tags/reverse-proxy/</link><description>Recent content in Reverse-Proxy on dev.endevour</description><generator>Hugo</generator><language>en-AU</language><lastBuildDate>Mon, 15 Apr 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://devendevour.iankulin.com/tags/reverse-proxy/index.xml" rel="self" type="application/rss+xml"/><item><title>NGINX Proxy Manager</title><link>https://devendevour.iankulin.com/nginx-proxy-manager/</link><pubDate>Mon, 15 Apr 2024 00:00:00 +0000</pubDate><guid>https://devendevour.iankulin.com/nginx-proxy-manager/</guid><description>&lt;p&gt;I&amp;rsquo;ve mentioned using NGINX as an &lt;a href="https://devendevour.iankulin.com/nginx-in-front-of-a-node-js-app/"&gt;interface between the internet and a service&lt;/a&gt; a while ago. This works by all incoming traffic coming to NGINX, and NGINX determining which service that traffic should go (from the NGINX config files) then acting as a middleman. This functionality is generally referred to as a &amp;lsquo;reverse proxy&amp;rsquo;.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devendevour.iankulin.com/images/nginx.png" alt="Terrible drawing of NGINX proxying requests off to different services." class="img-responsive"&gt; &lt;/p&gt;
&lt;p&gt;This is nice for a few reasons:&lt;/p&gt;</description></item></channel></rss>