<?xml version="1.0" encoding="UTF-8"?><html><body><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">

<channel>
	<title>Tiny WordPress Insights</title>
	<atom:link href="https://www.tinywp.in/feed/" rel="self" type="application/rss+xml"></atom:link>
	<link>https://www.tinywp.in
	<description>On WordPress core, plugins, themes, etc.</description>
	<lastbuilddate>Tue, 01 Jul 2025 15:09:19 +0000</lastbuilddate>
	<language>en-US</language>
	<sy:updateperiod>
	hourly	</sy:updateperiod>
	<sy:updatefrequency>
	1	</sy:updatefrequency>
	<generator>https://wordpress.org/?v=6.8.1</generator>
<site xmlns="com-wordpress:feed-additions:1">34390590</site>	<item>
		<title>FrankenPHP &ndash; A modern PHP server</title>
		<link>https://www.tinywp.in/frankenphp-server/
					<comments>https://www.tinywp.in/frankenphp-server/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Tue, 01 Jul 2025 12:02:25 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2719</guid>

					<description><a href="https://www.tinywp.in/frankenphp-server/" class="more-link">Continue reading<span class="screen-reader-text"> "FrankenPHP &ndash; A modern PHP server"</span></a>]]&gt;</description>
										<content:encoded>On May 15, 2025, FrankenPHP has become a part of PHP Foundation. It means that going forward, FrankenPHP will have more peer-reviewers and more help towards bug-fixes. FrankenPHP is already a stable platform and is already officially promoted by Caddy web server to run PHP apps such as WordPress, Laravel, Symfony, etc. If you&rsquo;d like to know the more in-depth info on all the&hellip;
<p><a href="https://www.tinywp.in/frankenphp-server/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/frankenphp-server/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2719</post-id>	</item>
		<item>
		<title>ssh-import-id-gh &ndash; Import your public SSH key from GitHub</title>
		<link>https://www.tinywp.in/ssh-import-id-gh/
					<comments>https://www.tinywp.in/ssh-import-id-gh/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Fri, 11 Aug 2023 12:29:21 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2682</guid>

					<description><a href="https://www.tinywp.in/ssh-import-id-gh/" class="more-link">Continue reading<span class="screen-reader-text"> "ssh-import-id-gh &ndash; Import your public SSH key from GitHub"</span></a>]]&gt;</description>
										<content:encoded>The (WordPress) developers often use to troubleshoot sites hosted in remote servers. While I don&rsquo;t recommend working with a production site directly, these days most hosted WP companies offer staging sites with SSH access, with wp-cli pre-installed. In order to log into those, most of us use password authentication that can lead to a number of security issues. For example&hellip;
<p><a href="https://www.tinywp.in/ssh-import-id-gh/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/ssh-import-id-gh/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2682</post-id>	</item>
		<item>
		<title>Bootstrapping DigitalOcean Servers</title>
		<link>https://www.tinywp.in/digitalocean-bootstrap/
					<comments>https://www.tinywp.in/digitalocean-bootstrap/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Thu, 26 Jan 2023 15:23:05 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2675</guid>

					<description><a href="https://www.tinywp.in/digitalocean-bootstrap/" class="more-link">Continue reading<span class="screen-reader-text"> "Bootstrapping DigitalOcean Servers"</span></a>]]&gt;</description>
										<content:encoded>I manage multiple DigitalOcean servers. There are a number of configurations to be done in order to bring a secure DO droplet. For example, firewall, alerts, etc. I missed a step years ago that caused a low priority security alert lately. So, I automated most of the steps while configuring any DigitalOcean server (new or old). Like most other things, I open-sourced the project in Github.
<p><a href="https://www.tinywp.in/digitalocean-bootstrap/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/digitalocean-bootstrap/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2675</post-id>	</item>
		<item>
		<title>What did I do in 2022 and my WishList for 2023</title>
		<link>https://www.tinywp.in/2022-review/
					<comments>https://www.tinywp.in/2022-review/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Fri, 16 Dec 2022 03:28:10 +0000</pubdate>
				<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2660</guid>

					<description><a href="https://www.tinywp.in/2022-review/" class="more-link">Continue reading<span class="screen-reader-text"> "What did I do in 2022 and my WishList for 2023"</span></a>]]&gt;</description>
										<content:encoded>It&rsquo;s the year of MikroTik and network engineering. So, there is hardly any WordPress stuff in this post. I bought MikroTik hAP AX2 this year, just after its launch. I&rsquo;d been waiting for it for years. This is my fourth MikroTik product for my R&amp;D. Earlier, I owned two numbers of hAP ac2 and SXT LTE Kit. One hAP AC2 runs on Router OS v6. The other one is on the latest version.
<p><a href="https://www.tinywp.in/2022-review/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/2022-review/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2660</post-id>	</item>
		<item>
		<title>TinyWP.in Infrastructure</title>
		<link>https://www.tinywp.in/infrastructure/
					<comments>https://www.tinywp.in/infrastructure/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Thu, 10 Nov 2022 15:02:22 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2630</guid>

					<description></description>
										<content:encoded>Back in 2011, I already wrote a colophon post. Nothing much changed in it in terms of underlying technologies used such as Nginx web server. However, a few things aren&rsquo;t mentioned in it, but will have a mention here. Basically, I am running most of the services using Google services for this domain (tinywp.in). Even though, I&rsquo;ve been trying to de-google myself for years, I still use Google&hellip;
<p><a href="https://www.tinywp.in/infrastructure/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/infrastructure/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2630</post-id>	</item>
		<item>
		<title>Rate limiting xmlrpc requests on WordPress using Nginx</title>
		<link>https://www.tinywp.in/xmlrpc-rate-limit-nginx/
					<comments>https://www.tinywp.in/xmlrpc-rate-limit-nginx/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Thu, 02 Dec 2021 02:02:30 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2609</guid>

					<description></description>
										<content:encoded>WordPress based sites are target for most automated bots. Those bots look for various vulnerability in WordPress core, the themes, and the plugins. Then, there are some kids (and their kid bots) that target specific resources in a WP site. &ldquo;xmlrpc.php&rdquo; is one such resource. It uses XML-RPC protocol that does many things in WordPress. For example, it helps with remote sites to notify their mentions&hellip;
<p><a href="https://www.tinywp.in/xmlrpc-rate-limit-nginx/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/xmlrpc-rate-limit-nginx/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2609</post-id>	</item>
		<item>
		<title>Disable PHP warnings when running wp-cli</title>
		<link>https://www.tinywp.in/disable-php-warnings-on-wp-cli/
					<comments>https://www.tinywp.in/disable-php-warnings-on-wp-cli/#comments</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Tue, 18 May 2021 14:46:00 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2577</guid>

					<description><a href="https://www.tinywp.in/disable-php-warnings-on-wp-cli/" class="more-link">Continue reading<span class="screen-reader-text"> "Disable PHP warnings when running wp-cli"</span></a>]]&gt;</description>
										<content:encoded>It is not uncommon to test sites on a development environment (locally or in a staging environment where others can see the work-in-progress). On a development environment, usually we have configured to be . Here&rsquo;s the sample of file in a development / test / staging environment&hellip; While the above code is perfectly okay, if the site creates PHP warnings, it is a nuisance to see them&hellip;
<p><a href="https://www.tinywp.in/disable-php-warnings-on-wp-cli/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/disable-php-warnings-on-wp-cli/feed/</wfw:commentrss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2577</post-id>	</item>
		<item>
		<title>Nginx compatibility for &ldquo;Cookies for Comments&rdquo; plugin</title>
		<link>https://www.tinywp.in/nginx-config-cookies-for-comments/
					<comments>https://www.tinywp.in/nginx-config-cookies-for-comments/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Thu, 29 Apr 2021 06:07:57 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=1438</guid>

					<description><a href="https://www.tinywp.in/nginx-config-cookies-for-comments/" class="more-link">Continue reading<span class="screen-reader-text"> "Nginx compatibility for &ldquo;Cookies for Comments&rdquo; plugin"</span></a>]]&gt;</description>
										<content:encoded>Whether you are aware or not, spammers are more interested in your site than anyone else. You&rsquo;ll understand this more vividly, when your blog starts to become famous and brings more and more visitors week after week, month after month, year after year. The most annoying thing about spam comments is the amount of time that you need to waste in dealing with it. There are some bright minds in&hellip;
<p><a href="https://www.tinywp.in/nginx-config-cookies-for-comments/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/nginx-config-cookies-for-comments/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1438</post-id>	</item>
		<item>
		<title>Buypass CA &ndash; SSL with 180 Days Validity</title>
		<link>https://www.tinywp.in/buypass-ssl-certificate/
					<comments>https://www.tinywp.in/buypass-ssl-certificate/#comments</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Tue, 21 Apr 2020 14:45:00 +0000</pubdate>
				<category></category>
		<category></category>
		<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2494</guid>

					<description><a href="https://www.tinywp.in/buypass-ssl-certificate/" class="more-link">Continue reading<span class="screen-reader-text"> "Buypass CA &ndash; SSL with 180 Days Validity"</span></a>]]&gt;</description>
										<content:encoded>Buypass is a Certificate Authority (CA) based on Europe. It offers free SSL certificates with a validity of 180 days. Unlike LetsEncrypt, Buypass CA also offers paid SSL too. So, it is neither a competitor to LetsEncrypt, nor it is a nonprofit. It is a for-profit company that also offers free SSL certificates. There are other CAs that offer free SSL certificates too. However&hellip;
<p><a href="https://www.tinywp.in/buypass-ssl-certificate/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/buypass-ssl-certificate/feed/</wfw:commentrss>
			<slash:comments>3</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2494</post-id>	</item>
		<item>
		<title>Version Control</title>
		<link>https://www.tinywp.in/version-control/
					<comments>https://www.tinywp.in/version-control/#respond</comments>
		
		<dc:creator></dc:creator>
		<pubdate>Wed, 10 Jul 2019 12:31:37 +0000</pubdate>
				<category></category>
		<guid ispermalink="false">https://www.tinywp.in/?p=2439</guid>

					<description><a href="https://www.tinywp.in/version-control/" class="more-link">Continue reading<span class="screen-reader-text"> "Version Control"</span></a>]]&gt;</description>
										<content:encoded>WordPress uses SVN internally such as for plugins repository. So, a plugin author must use SVN tools to upload a plugin and update the existing plugin/s in wp.org plugins repository. If you are new to SVN, WordPress docs team has a nice guide to get started with SVN and plugins repository. The best practices section is a gem. It is possible to update WP core using SVN. However&hellip;
<p><a href="https://www.tinywp.in/version-control/" rel="nofollow">Source</a></p>]]&gt;</content:encoded>
					
					<wfw:commentrss>https://www.tinywp.in/version-control/feed/</wfw:commentrss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">2439</post-id>	</item>
	</channel>
</rss>
</body></html>

<!-- Cached page generated by WP-Super-Cache on 2025-07-01 20:51:53 -->

<!-- Compression = gzip -->