<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>links.lmorchard.com - #nginx</title>
    <link>/tags/nginx/</link>
    <description>Recent bookmarks tagged #nginx</description>
    <lastBuildDate>Mon, 02 Nov 2026 08:24:50 +0000</lastBuildDate>
    <item>
      <title>How to set up your own private RTMP server using nginx | Open Broadcaster Software</title>
      <link>https://obsproject.com/forum/resources/how-to-set-up-your-own-private-rtmp-server-using-nginx.50/</link>
      <description>Most people who stream enjoy using services such as Twitch.tv or Ustream to deliver video to viewers, and that works well enough. But sometimes you want some more control over your stream, or you want other people to be able to stream to you, or you want to stream to multiple places, or any number of things that requires you to have access to an actual RTMP stream from an RTMP server. This guide will cover the very basics of setting up a simple RTMP server on a Linux computer. Don&#39;t worry, it&#39;s not too complicated, but having familiarity with Linux will certainly help.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #imported:pinboard #nginx #rtmp #server #streaming #video&lt;/p&gt;</description>
      <pubDate>Sat, 07 Jul 2018 03:05:38 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:31290</guid>
      <category>imported:pinboard</category>
      <category>nginx</category>
      <category>rtmp</category>
      <category>server</category>
      <category>streaming</category>
      <category>video</category>
    </item>
    <item>
      <title>How to set up your own private RTMP server using nginx | Open Broadcaster Software</title>
      <link>https://obsproject.com/forum/resources/how-to-set-up-your-own-private-rtmp-server-using-nginx.50</link>
      <description>Most people who stream enjoy using services such as Twitch.tv or Ustream to deliver video to viewers, and that works well enough. But sometimes you want some more control over your stream, or you want other people to be able to stream to you, or you want to stream to multiple places, or any number of things that requires you to have access to an actual RTMP stream from an RTMP server. This guide will cover the very basics of setting up a simple RTMP server on a Linux computer. Don&#39;t worry, it&#39;s not too complicated, but having familiarity with Linux will certainly help.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #nginx #rtmp #server #streaming #video&lt;/p&gt;</description>
      <pubDate>Sat, 07 Jul 2018 03:05:38 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:27768</guid>
      <category>nginx</category>
      <category>rtmp</category>
      <category>server</category>
      <category>streaming</category>
      <category>video</category>
    </item>
    <item>
      <title>HTTP 413 Request Entity Too Large – Control+R</title>
      <link>http://jontai.me/blog/2012/04/http-413-request-entity-too-large/</link>
      <description>Adding client_max_body_size 8M; to the server { ... } section of my nginx configuration fixed the problem.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #imported:pinboard #nginx #uploads #webdev #wordpress&lt;/p&gt;</description>
      <pubDate>Sun, 10 Feb 2013 02:02:33 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32495</guid>
      <category>imported:pinboard</category>
      <category>nginx</category>
      <category>uploads</category>
      <category>webdev</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>HTTP 413 Request Entity Too Large – Control+R</title>
      <link>http://jontai.me/blog/2012/04/http-413-request-entity-too-large</link>
      <description>Adding client_max_body_size 8M; to the server { ... } section of my nginx configuration fixed the problem.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #nginx #uploads #webdev #wordpress&lt;/p&gt;</description>
      <pubDate>Sun, 10 Feb 2013 02:02:33 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23236</guid>
      <category>nginx</category>
      <category>uploads</category>
      <category>webdev</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>Nginx, Django, and X-Accel-Redirects — The Wellfire Blog</title>
      <link>http://www.wellfireinteractive.com/blog/nginx-django-x-accel-redirects/</link>
      <description>Like Apache’s mod_xsendfile, Nginx’s X-Accel module provides for internal redirects. An x-accel-redirct is internal because instead of redirecting the client’s request to another URL, it redirects the location of Nginx’s request to another resource.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #django #imported:pinboard #nginx #python #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 06 Feb 2013 20:39:30 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:32503</guid>
      <category>django</category>
      <category>imported:pinboard</category>
      <category>nginx</category>
      <category>python</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Nginx, Django, and X-Accel-Redirects — The Wellfire Blog</title>
      <link>http://www.wellfireinteractive.com/blog/nginx-django-x-accel-redirects</link>
      <description>Like Apache’s mod_xsendfile, Nginx’s X-Accel module provides for internal redirects. An x-accel-redirct is internal because instead of redirecting the client’s request to another URL, it redirects the location of Nginx’s request to another resource.&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #django #nginx #python #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 06 Feb 2013 20:39:30 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:23219</guid>
      <category>django</category>
      <category>nginx</category>
      <category>python</category>
      <category>webdev</category>
    </item>
    <item>
      <title>NGINX + PHP-FPM + APC = Awesome</title>
      <link>http://interfacelab.com/nginx-php-fpm-apc-awesome</link>
      <description>&#34;The following guide will walk you through setting up possibly the fastest way to serve PHP known to man. If there is a faster way, I’ve not yet found it climbing through zillions of blog posts out there on the subject. In this article, we’ll be installing nginx http server, PHP with the PHP-FPM patches, as well as APC. The end result? Pure awesome.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #apache #apc #nginx #performance #php #webdev&lt;/p&gt;</description>
      <pubDate>Sat, 05 Jun 2010 17:01:57 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:13479</guid>
      <category>apache</category>
      <category>apc</category>
      <category>nginx</category>
      <category>performance</category>
      <category>php</category>
      <category>webdev</category>
    </item>
    <item>
      <title>Holy Shmoly! » WordPress, Nginx and WP Super Cache</title>
      <link>http://ocaoimh.ie/89495533/wordpress-nginx-wp-super-cache</link>
      <description>&#34;If you host your own WordPress blog, it’s probably on Apache. That all fine and good. For most sites Apache works wonderfully, especially as it’s so easy to find information on it, on mod_rewrite and everything else that everyone else uses.&#xA;&#xA;One of the alternatives is Nginx, a really fast webserver that streaks ahead of Apache in terms of performance, but isn’t quite as easy to use. That’s partly because Apache is the default webserver on most Linux distributions and hosts. Want to try Nginx? Here’s how.&#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #caching #metablogging #nginx #webdev #wordpress&lt;/p&gt;</description>
      <pubDate>Tue, 24 Nov 2009 17:58:24 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:12646</guid>
      <category>caching</category>
      <category>metablogging</category>
      <category>nginx</category>
      <category>webdev</category>
      <category>wordpress</category>
    </item>
    <item>
      <title>Django snippets: minimal nginx conf to split get/post requests</title>
      <link>http://www.djangosnippets.org/snippets/1141</link>
      <description>&#34;After a point the sql server becomes the bottleneck in lots of web application, and to scale, master-slave replication with single master, multiple slave is recommended. This setup with nginx can be used to accomplish traffic distribution between master and slave based on request method. &#34;&lt;br/&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tags:&lt;/strong&gt; #config #get #http #master #nginx #post #scalability #slave #sysadmin #webdev&lt;/p&gt;</description>
      <pubDate>Wed, 15 Oct 2008 19:37:44 +0000</pubDate>
      <guid isPermaLink="false">linkding-ssg:bookmark:11541</guid>
      <category>config</category>
      <category>get</category>
      <category>http</category>
      <category>master</category>
      <category>nginx</category>
      <category>post</category>
      <category>scalability</category>
      <category>slave</category>
      <category>sysadmin</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
