v0.2.4

• ❄️ New upload_vendors option which default to false. When set to true this option will (during an upload strategy only) skip the deploy:vendors task and include the vendor folder in your upload. (See #18)
• 🚑 Fix the following issue on windows "'vendor' is not recognized as an internal or external command" by using a relative path to the compiled deploy.php file. (See #22)
• 🚑 The commands executed by Laravel Deploy now returns an appropriate exit code. Formerly, it was throwing an exception but the returned status code was always 0. (See #41)
• 🚑 Other small bug fixes.

v0.2.3

• 📥 New upload strategy. Uploads a production-ready folder directly within a new release. Read more.
• ⚠️ Changed default upload options. When uploading either via the local strategy or the upload strategy, it will now exclude the /vendor folder instead of the vendor pattern. That is, only the vendor folder at the root of your project will be excluded. (See #14)
• 🚑 Small bug fixes.

v0.2.2

Small bug fixes

v0.2.1

• 📄 Reload php-fpm in set up. When you run php artisan deploy:init and you are not using Laravel Forge, the command will ask you if you want to reload php-fpm after each deployment. (Using Laravel Forge default to reloading php-fpm). The command will then ask you which php version you are using. This information will be used to reload php-fpm using the right service. E.g. if you enter 7.0 it will reload the php7.0-fpm service. This can than be edited in the config/deploy.php file as the php_fpm_service option.

• ⬇️ Import recipe/laravel.php. Laravel Deployer now has better control over artisan tasks and Laravel specific options.

  • The task artisan:migrate is now skipped with a warning if the .env file is inexistant or empty. This situation typically arises on first deployments and blocks the user from being able to edit their production environment after a first deployment.
  • ⚠️ Did not import the redondant deploy:public_disk task since artisan:storage:link already takes care of creating a symlink between public/storage and the public disk.

v0.2

What's new?

• 📝 New configuration file. Configure your deployments via a traditional config/deploy.php file. In there you can configure your hosts, options, hooks, default strategy and even create new strategies without having to get your hand dirty in the Deployer namespace.

• 🃏Deployment strategies. Choose amongst several deployment strategies or create your own strategies. Supported so far: basic (the default strategy of v0.1), firstdeploy (for migrating folder structure when using Laravel Deployer for the first time), local (for building assets locally before uploading them) and pull (for a quick no-zero-downtime git pull on the server).

• 🔈 Dump that laravel.log without connecting to your server. Simply run php artisan logs and it will dump the last 200 lines of your laravel.log without the error stacks. Of course, you can configure that behaviour via the log_lines and log_command options.

• 🖥 Useful information in the console. Upon deployment of every host, get an information message that let you know which strategy is being used for that particular deployment. Get the total execution time of your deployments in a success message.

How to upgrade from v0.1

1. Run php artisan deploy:init again to generate your new config/deploy.php file.
2. Compare this with your previous deploy.php file at the root of your project. If you've manually added some hooks or customised some options, make sure you reflect those changes on the new config/deploy.php file.
3. Delete your old deploy.php file at the root of your project.
4. Deploy 🚀

v0.1.5

Small bug fixes

v0.1.4

• Shallow hooks (doc)
• Locally build deployment strategy (doc)
• Disable git_tty and allow_anonymous_stats by default (commit)
• deploy:rollback artisan command (commit)

v0.1.3

Support Lumen deployments.

v0.1.2

:white_check_mark: Test Firstdeploy shared

v0.1.1

• Finish documentation
• Add php-fpm reloading by default when using Laravel Forge