You shouldn't be running composer update on your deployment, just composer install which doesn't take as much memory since it doesn't have to resolve dependencies.
Would be nice to be able to customize keys, choose a format for a list of a resource, etc. so that if you use this in development you don't need to make changes for your "real" API if you have different standards.
It's installed through Composer. In composer.json it sets up a custom repository to download the latest version of WordPress, and then uses the "extra" section to install it to a custom directory (in this case the public directory).
Yeah I don't understand the use of statics here. I'm going to guess it's just so they can use the "nicer" syntax without having to instantiate a new object, which would honestly make more sense to me. That way you can inject a Link instance into your controller/views and just call `$link->route('namedRoute')`.
At least some large cloud storage providers offer it. For example, AWS has Import/Export[0] and Google has Offline Disk Import for Google Cloud Storage[1].
One other problem is that if you're using a tool like Capistrano to deploy, you usually set your remote repo to Github. When Github goes down, you can't deploy until it comes back up or you set up your own remote server.
I've tried the last two major versions of PHPStorm and I just can't use it. On my Air with 4GB of RAM it struggles to even open a file. It's slow, sometimes unresponsive, and uses so much memory so my VM can't run on the same machine. If there was a 'Lite' version, I'd love to try it out. But the defacto PHP IDE can not run on my machine, which is why I stick with ST and plugins.
> Mr. Thursfield has done much of the renovation work himself, including woodworking.