Laravel hosting

Reliable Laravel hosting comes down to five checks: queue workers that keep running, a scheduler that fires every minute, deploys that go live only after a successful build, a managed MySQL database, and backups that run without anyone starting them. On fortrabbit, php artisan queue:work runs as a long-running worker and schedule:run as a cron job, both in the jobs component; a worker plus the scheduler needs Jobs SM at €3 a month. A push to the connected GitHub branch runs Composer and npm in a build, and the release goes live atomically, so a failed build leaves the old version serving. MySQL is a separate component that autoscales into the next plan when it fills up. Backups run every 24 hours, from one copy up to 48. SSH covers artisan, tinker and migrations, and the PHP version is picked per environment. Every new app starts a seven-day trial without a credit card.

# Laravel hosting at fortrabbit

Laravel is a popular open-source PHP framework that was written and is still being led by Taylor Otwell. It's well on its way to becoming the de facto standard for web application frameworks on the internet. It's easy to get started with, yet powerful. It has a vast ecosystem with many third-party services and additional software built on top of it, such as Statamic and October CMS. Laravel is free open source software. The venture backed Laravel Inc also offers commercial hosting services.

We know Laravel well. Our initial platform version was mostly built for Laravel. It was also mostly built with Laravel. Today, we are supporting a wider range of applications. But fortrabbit partly still runs Laravel, side by side with Symfony. Installing Laravel on fortrabbit is straightforward: deploy with git push and Composer installs the dependencies during the build. Extensive docs you can follow from A-Z including deployment and tuning are at your disposal. Eye to eye developer support is included with the service. fortrabbit's Laravel hosting may cost you less than your current solution. Coming from a dyno-based setup? The Heroku migration path walks through what maps over and what does not.