With Envoyer you can easily deploy your PHP projects without any downtime. You can connect your Github, BitBucket or any other git source and let Envoyer deploy your application to one or more servers. Although Envoyer is made by Taylor Otwell, the developer who created Laravel, it’s not restricted to Laravel. You can deploy any PHP project and is pretty affordable too.
Unfortunately not all your packages can be open source. Some companies don’t join the “open source train” while other packages must remain private for other reasons. These packages can be used in several projects and it would be lovely to use it just like any other package. Off course you use the private version of packagist but that’s a bit expensive (starting at 49 euro per month) and just isn’t necessary.
Laravel can be installed with the Laravel installer or composer. Both installers will place the application into a folder which is named after the application. Sometimes we want to affect that behaviour.
There are many packages available for asset management in Laravel. Although some are pretty good, I think asset management packages aren’t really necessary in Laravel thanks to the Blade template engine. So with those words, let’s put my money where my mouth is and show you the way I’m managing my assets in Laravel.
In Laravel 5 the HTML and Form builder got removed because it shouldn’t be in the core of the framework. I can see their point there, but if you are upgrading your project it would be a lot of work to change all those calls. So I want to get the HTML and form builder back. The Laravel Collective maintains (and improve) packages which are removed from Laravel. The HTML and Form package from them is preferred over the
illuminate/html package, because it’s better maintained. So let’s add their package to our Laravel installation.
Currently I’m converting my Laravel 4 application to Laravel 5. When finding tricks or goofs I will post it to this blog.
One of the first thing I’m doing after installing Laravel is changing the public directory. In Laravel 4 it was pretty straight forward, just edit the
bootstrap/paths.php. Unfortunately in Laravel 5 it’s a bit more tricky, but not that hard either.