<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
<title>fortrabbit blog — Erin Strand</title>
<link>https://blog.fortrabbit.com/author/es</link>
<description><![CDATA[Articles from the fortrabbit blog written by Erin Strand.]]></description>
<language>en</language>
<lastBuildDate>Tue, 22 Sep 2026 07:39:21 GMT</lastBuildDate>
<ttl>10</ttl>
<atom:link href="https://blog.fortrabbit.com/feeds/author/es" rel="self" type="application/rss+xml" />
<item>
<title>MySQL 8.4 upgrade plan</title>
<link>https://blog.fortrabbit.com/mysql-8-4-upgrade-plan</link>
<guid isPermaLink="true">https://blog.fortrabbit.com/mysql-8-4-upgrade-plan</guid>
<pubDate>Tue, 26 May 2026 11:00:00 GMT</pubDate>
<author>Erin Strand</author>
<category>changelog</category>
<description><![CDATA[Two ways to upgrade an app on the old fortrabbit platform from MySQL 8.0 to 8.4, now that 8.4 is the default for new apps. MySQL 8.4 is now the default for newly created fortrabbit apps. This guide covers two methods for upgrading your existing (old platform) App before we will retire MySQL 8.0 in June 2026.]]></description>
<content:encoded><![CDATA[<p>Two ways to upgrade an app on the old fortrabbit platform from MySQL 8.0 to 8.4, now that 8.4 is the default for new apps. MySQL 8.4 is now the default for newly created fortrabbit apps. This guide covers two methods for upgrading your existing (old platform) App before we will retire MySQL 8.0 in June 2026.</p>]]></content:encoded>
</item>
<item>
<title>The story of our new ENV vars edit experience</title>
<link>https://blog.fortrabbit.com/our-new-env-var-edit-experience</link>
<guid isPermaLink="true">https://blog.fortrabbit.com/our-new-env-var-edit-experience</guid>
<pubDate>Wed, 08 Apr 2026 08:38:48 GMT</pubDate>
<author>Erin Strand</author>
<category>chronicles</category>
<description><![CDATA[Building an environment variable editor that handles multiline values, special characters and a base64 helper without feeling clever. Editing ENV vars should be easy, right? Here's how we iterated to make it more powerful and developer-friendly, tackling devilish details.]]></description>
<content:encoded><![CDATA[<p>Building an environment variable editor that handles multiline values, special characters and a base64 helper without feeling clever. Editing ENV vars should be easy, right? Here's how we iterated to make it more powerful and developer-friendly, tackling devilish details.</p>]]></content:encoded>
</item>
<item>
<title>PHP 8.5</title>
<link>https://blog.fortrabbit.com/php-85-update</link>
<guid isPermaLink="true">https://blog.fortrabbit.com/php-85-update</guid>
<pubDate>Tue, 17 Feb 2026 10:44:59 GMT</pubDate>
<author>Erin Strand</author>
<category>changelog</category>
<description><![CDATA[PHP 8.5 is live on both platforms: selectable in the dashboard, default for new apps, and available through the latest setting. We finally rolled out PHP 8.5 and here are the details.]]></description>
<content:encoded><![CDATA[<p>PHP 8.5 is live on both platforms: selectable in the dashboard, default for new apps, and available through the latest setting. We finally rolled out PHP 8.5 and here are the details.</p>]]></content:encoded>
</item>
<item>
<title>Testing code for PHP 7</title>
<link>https://blog.fortrabbit.com/php-testing</link>
<guid isPermaLink="true">https://blog.fortrabbit.com/php-testing</guid>
<pubDate>Wed, 19 Sep 2018 00:00:00 GMT</pubDate>
<author>Erin Strand</author>
<category>webdev</category>
<description><![CDATA[Run automated compatibility checks against PHP 7.2 before switching a live app, and catch the breaking changes ahead of time. This post helps running automated tests on your code to detect breaking changes before switching the PHP version. It includes instructions on how to use our predefined Docker image with PHPCompatibility.]]></description>
<content:encoded><![CDATA[<p>Run automated compatibility checks against PHP 7.2 before switching a live app, and catch the breaking changes ahead of time. This post helps running automated tests on your code to detect breaking changes before switching the PHP version. It includes instructions on how to use our predefined Docker image with PHPCompatibility.</p><figure><img src="https://blog.fortrabbit.com/images/php7-testing.gif" alt="Testing code for PHP 7" /></figure>]]></content:encoded>
</item>
<item>
<title>PHP 7.2 upgrade path</title>
<link>https://blog.fortrabbit.com/php-upgrade-path</link>
<guid isPermaLink="true">https://blog.fortrabbit.com/php-upgrade-path</guid>
<pubDate>Wed, 19 Sep 2018 00:00:00 GMT</pubDate>
<author>Erin Strand</author>
<category>webdev</category>
<description><![CDATA[Security support for PHP 5.6 and 7.0 ends in December 2019. The minimum-effort route to move an app to PHP 7.2 before then. The official security support for PHP 5.6 and PHP 7.0 will end in December 2019. We plan to force-update all Apps on those versions to PHP 7.1 in February 2019. The exact date will be announced. We recommend you to update well before that. Here is how, exactly.]]></description>
<content:encoded><![CDATA[<p>Security support for PHP 5.6 and 7.0 ends in December 2019. The minimum-effort route to move an app to PHP 7.2 before then. The official security support for PHP 5.6 and PHP 7.0 will end in December 2019. We plan to force-update all Apps on those versions to PHP 7.1 in February 2019. The exact date will be announced. We recommend you to update well before that. Here is how, exactly.</p><figure><img src="https://blog.fortrabbit.com/images/php56-php72-migrate-poster.png" alt="PHP 7.2 upgrade path" /></figure>]]></content:encoded>
</item>
</channel>
</rss>