Cookies ahead

Our support chat tool "Intercom" would like to collect some more data on you. See the related link for more details.

Docs

fortrabbit blog

RSS— tag opinion

2012

D
Code in git, dependencies in Composer, assets in object storage, mail in a service: the case for modular, decoupled hosting.
W
IaaS, PaaS, bare metal, shared or managed hosting: how to decide, written for clients whose old hosting platform was being retired.
G
The cloud: economically attractive, but what the about ecological impact?
T
Brutal price competition produces factory farming in meat and something similar in hosting. An illustrated argument about cheap.
R
Going generally available without a public beta period: the case for launching a hosting service early and iterating in the open.
P
A collection of links on the modern side of PHP, gathered when the language was shaking off its spaghetti-code reputation.
F
Building a PaaS in Berlin without venture capital: what bootstrapping decides about pricing, pace and the product itself.
T
A manifest for what a PHP platform as a service should do, written in 2012 when none of the existing ones came close to it.
B
What 160 developers told us about their PHP workflows, hosting and tools, and how the answers shaped the platform we then built.
W
The www subdomain is optional, hard to say out loud, and still everywhere. On apex domains, print designers and old internet habits.
O
A first look at browser-based code editors and web IDEs in 2012 — what the category promised, and whether it was any good yet.
T
Will small hosting plans end up free? Someone always pays for the resources — a look at freemium in hosting after AppFog's pricing.
V
How locked in is a website to its hosting provider, and does portability across clouds mean anything in practice for a PHP app?
A
New-school cloud or legacy LAMP style — what's state of the art in PHP hosting?
C
A 2012 snapshot of the PHP PaaS field — Heroku, PHP Fog, Pagodabox, dotCloud, cloudControl and the European newcomers. Most of them are gone.