nginx

Sysadmin extraordinaire Stefano Marinelli (<span class="h-card"><a href="https://mastodon.bsd.cafe/@stefano" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stefano</span></a></span>) has written this great, concise article on how to tune <a href="/tags/nginx/" rel="tag">#nginx</a> to improve <a href="/tags/snac/" rel="tag">#snac</a> performance while serving media like images or videos.<br><br><a href="https://it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/" rel="nofollow" class="ellipsis" title="it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/"><span class="invisible">https://</span><span class="ellipsis">it-notes.dragas.net/2025/01/29</span><span class="invisible">/improving-snac-performance-with-nginx-proxy-cache/</span></a><br><br>

<p>⁂ Postawiłem sobie dzisiaj pl-fe od Nicole <span class="h-card"><a href="https://pl.fediverse.pl/users/mkljczk" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mkljczk</span></a></span> dla mojego <a href="/tags/gotosocial/" rel="tag">#GoToSocial</a> Fedika.pl </p><p>Z małym zgrzytem. <a href="/tags/nginx/" rel="tag">#Nginx</a> wymagał drobnej korekty location. To pomyślałem że podzielę się, bo może ktoś się odbije od tego samego. Tu akurat domyślna konfiguracja nginx w <a href="/tags/yunohost/" rel="tag">#YunoHost</a>-owej apce &quot;My webapp&quot; nie zadziałała. Wyskakiwały 404 przy logowaniu do domeny instancji.</p><p>Domyślne location było:</p><p>try_files $uri $uri/ /index.php?$args =404; </p><p>a powinien być dodany index.html, bo to przecież <a href="/tags/spa/" rel="tag">#SPA</a> / <a href="/tags/pwa/" rel="tag">#PWA</a>:</p><p>try_files $uri $uri/ /index.html =404;</p><p>Niniejszym macie receptę jak do swoich GtSów na YunoHost dodać własne <a href="/tags/plfe/" rel="tag">#plfe</a>. </p><p>Polecam, to najlepszy klient webowy i na telefon 👍 </p><p>P.S. Zacznę chyba nazywać <a href="/tags/nicolefe/" rel="tag">#NicoleFE</a> bo mi się pl-fe średnio podoba 😉</p><p><a href="/tags/fedipomoc/" rel="tag">#FediPomoc</a> <a href="/tags/feditipspl/" rel="tag">#FediTipsPL</a></p>

<p>Anyone else use NGINX Proxy Manager in their homelab? I’ve had some real issues with caching enabled on some self hosted fedi apps. </p><p><a href="/tags/homelab/" rel="tag">#HomeLab</a> <a href="/tags/nginx/" rel="tag">#Nginx</a></p>

<p>Dear fellow or potential fellow gotosocial instance admins,<br>I&#x27;ve come up with a novel way to set up a <a href="/tags/gotosocial/" rel="tag">#gotosocial</a> server behind a reverse proxy, which avoids the use of making new firewalling rules - both on a VPS, and creating port forwarding on one&#x27;s home router. This method is ideal for minimizing the cost of running one&#x27;s own <a href="/tags/activitypub/" rel="tag">#ActivityPub</a>/<a href="/tags/mastodon/" rel="tag">#Mastodon</a> server, in a way that leverages inexpensive fast storage on the backend (say, on a <a href="/tags/raspberrypi/" rel="tag">#RaspberryPi</a> 5, 2GB of RAM, with an NVMe). As many valiant and praiseworthy Mastodon server admins might attest to, renting cloud VPS&#x27; can cost a lot, especially when storing many tens or hundreds of GB of user data.</p><p>My method avoids the need of forwarding ports 443 and 80 into one&#x27;s home LAN, using DNAT (on the VPS) and port forwarding (on one&#x27;s home router). In a nutshell, it&#x27;s a novel use of <a href="/tags/wireguard/" rel="tag">#Wireguard</a>, in conjunction with <a href="/tags/nginx/" rel="tag">#nginx</a> on the frontend, and gotosocial on the backend. This can save the cost of renting a dedicated VPS, to get the exclusive use of ports 443 and 80, in conjunction with static IPv4 and IPv6 addresses. My method optimizes on reliability and cheapness, but it&#x27;s not the most secure - decryption and re-encryption happens on the VPS, before the data travels down the Wireguard tunnel. This exposes the data to any underlying hypervisor at one&#x27;s hosting company. So full disclosure there.</p><p>I&#x27;ve run my method by the helpful gotosocial furries in their <a href="/tags/matrix/" rel="tag">#Matrix</a> Help chatroom (and I&#x27;m grateful for their help to debug subtle warts the method had), and got their blessing, at least to the technical soundness of the method.</p><p>I have a testing instance of gotosocial 0.21.0 set up with this new method: <a href="https://g.toque.im" rel="nofollow"><span class="invisible">https://</span>g.toque.im</a></p><p>I&#x27;m the user <span class="h-card"><a href="https://g.toque.im/@owl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>owl</span></a></span> on that instance, should you wish to befriend me there.</p><p>I&#x27;ll make a longer blog post on this in the days to come, and post it in a reply to this post. (I also cross-posted this on another account of mine, please forgive the duplicate: <span class="h-card"><a href="https://wiseowl.club/@gtsadmin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>gtsadmin</span></a></span> )</p><p><a href="/tags/devops/" rel="tag">#DevOps</a> <a href="/tags/linux/" rel="tag">#Linux</a> <a href="/tags/infosec/" rel="tag">#infosec</a> <a href="/tags/selfhosting/" rel="tag">#SelfHosting</a> <a href="/tags/datasovereignty/" rel="tag">#DataSovereignty</a> <a href="/tags/opensource/" rel="tag">#OpenSource</a></p>

<p>🎬 Skryptowanie nginx-a za pomocą js-a. Case study na rzecz wydajności i prywatności</p><p><span class="h-card"><a href="https://toot.kuba-orlik.name/@kuba" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>kuba</span></a></span> z Fundacji <span class="h-card"><a href="https://mastodon.internet-czas-dzialac.pl/@icd" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>icd</span></a></span> pokazuje, jak wykorzystać <a href="/tags/javascript/" rel="tag">#JavaScript</a> do skryptowania <a href="/tags/nginx/" rel="tag">#NGINX</a> oraz jak ta technika może poprawić wydajność i zwiększyć prywatność użytkowników.</p><p>👉 PeerTube: <a href="https://tube.pol.social/w/2BbPBaXKQU1c2QCEThGQNR" rel="nofollow" class="ellipsis" title="tube.pol.social/w/2BbPBaXKQU1c2QCEThGQNR"><span class="invisible">https://</span><span class="ellipsis">tube.pol.social/w/2BbPBaXKQU1c</span><span class="invisible">2QCEThGQNR</span></a><br>👉 YouTube: <a href="https://www.youtube.com/watch?v=O8wkSDxssLw" rel="nofollow" class="ellipsis" title="www.youtube.com/watch?v=O8wkSDxssLw"><span class="invisible">https://</span><span class="ellipsis">www.youtube.com/watch?v=O8wkSD</span><span class="invisible">xssLw</span></a></p><p><a href="/tags/piwo/" rel="tag">#PIWO</a> <a href="/tags/piwo2025/" rel="tag">#PIWO2025</a> <a href="/tags/opensource/" rel="tag">#opensource</a> <a href="/tags/freesoftware/" rel="tag">#freesoftware</a> <a href="/tags/prywatność/" rel="tag">#prywatność</a> <a href="/tags/poznań/" rel="tag">#poznań</a></p>

<p>Sooooo my recent mishaps with server administration are making me speed up my plans of shifting towards community-owned and -maintained hosting.</p><p>Ever since my conversation with <span class="h-card"><a href="https://cosocial.ca/@boris" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>boris</span></a></span> almost one year ago, I took his quote “self-hosting is selfish” as a mantra. It’s time to act accordingly.</p><p>Together with <span class="h-card"><a href="https://pan.rent/@Holly" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Holly</span></a></span> and <span class="h-card"><a href="https://pan.rent/@youjungnoh" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>youjungnoh</span></a></span>, we are putting together a group of tech-savy people who want to, respectively:</p><p>Learn more about system administration<br>Get their hands dirty while doing so<br>Maintain our own shared server<br>Host their own things (be them websites, projects, or services) together with comrades instead of individual infrastructure.</p><p>There are many super cool collectives that are doing this already, and we intend to draw inspiration from their work and their documentation, but we really want to do this together!</p><p>Who wants to join? Please, do reach out! I already spun up a small-ish VPS that is now hosting all my static websites. If you’d like to get involved, reach out and I would be happy to give you SSH access 🌻</p><p>We would also be very grateful if more experienced sysAds want to help us out by hosting workshops or brief classes.</p><p>We intend to meet for the first time in South Holland (but maybe virtually too) sometime during the first two weeks of March.</p><p>Next steps:</p><p>Find a name for this group/server/mission<br>Plan a series of (free, open) intro lessons with guests<br>Start hosting some things<br>Migrate things I am already hosting with YunoHost in our community server<br>Migrate to a physical device in a home of ours?</p><p>EDIT: I forgot to add this, but it goes without saying that ours would be a queer and transfeminist server</p><p><a href="/tags/communityhosting/" rel="tag">#communityHosting</a> <a href="/tags/linux/" rel="tag">#Linux</a> <a href="/tags/sysad/" rel="tag">#sysAd</a> <a href="/tags/systemadministration/" rel="tag">#systemAdministration</a> <a href="/tags/selfhosting/" rel="tag">#selfHosting</a> <a href="/tags/yunohost/" rel="tag">#YunoHost</a> <a href="/tags/nginx/" rel="tag">#Nginx</a> <a href="/tags/hosting/" rel="tag">#hosting</a> <a href="/tags/server/" rel="tag">#server</a> <a href="/tags/vps/" rel="tag">#VPS</a></p>

<p>My <a href="/tags/starterpack/" rel="tag">#StarterPack</a> for <a href="/tags/linux/" rel="tag">#Linux</a> <a href="/tags/selfhosting/" rel="tag">#SelfHosting</a><br>1) Heimdall start page for your LAN<br>2) Shiori bookmarks<br>3) Copyparty for filesharing through web or FTP<br>4) Kanboard Kanban board<br>5) Kiwix for offline website content<br>6) calibre-web for ebooks<br>7) Hyper8 for self-hosted video content, like a poor man&#x27;s <a href="/tags/youtube/" rel="tag">#Youtube</a>.<br>8) mkdocs for a markdown-based wiki</p><p>I self-host all of these, using <a href="/tags/nginx/" rel="tag">#nginx</a> as the web server in all cases. These all consume very little RAM and CPU, and would run very performantly on a Raspberry Pi 5 2GB, with a decent SSD. No <a href="/tags/docker/" rel="tag">#docker</a> needed for any of them.<br><a href="/tags/opensource/" rel="tag">#OpenSource</a> <a href="/tags/datasovereignty/" rel="tag">#DataSovereignty</a></p>