Laravel Forge: Hello World to Hello Production
19 likes8,135 views
The document outlines the process of developing and deploying a Laravel application using Laravel Forge and Homestead. It emphasizes creating a local development environment with Vagrant, configuring Homestead, automating testing, and implementing continuous delivery for production. It also highlights various tools, resources, and best practices for managing server configurations and deployments effectively.
Laravel Forge: Hello World to Hello Production
- 1. Laravel Forge: From Hello World to Hello Production
- 2. Step One: Hello World Step Two: CI, CD, OMG Step Three: ???? Step Four: Hello Production
- 3. Step One: Hello World
- 4. Create our project Via Laravel Installer: laravel new hello-world Via Composer: composer create-project laravel/laravel hello-world --prefer-dist
- 5. Where should our project live? I prefer to keep things in ~/PhpstormProjects
- 6. MAMP, LAMP, WAMP, WAT? Mac/Linux/Windows Apache MySQL PHP These are all great tools
- 7. Is your server running MAMP?
- 8. Why not develop ON the server?
- 9. Do not develop ON the server
- 10. Develop in the same environment
- 12. Virtual Machines are cheap
- 13. Our Use Case: Duplicate our server environment in a local virtual machine
- 14. Installing an OS takes time
- 15. Vagrant!
- 16. Vagrant allows you to: • Create a server • Configure a server • Delete a server …over and over and over..
- 17. Which Vagrant?
- 18. Homestead “Laravel Homestead is an official, pre-packaged Vagrant "box" that provides you a wonderful development environment without requiring you to install PHP, HHVM, a web server, and any other server software on your local machine.”
- 19. But I need…
- 20. What’s in the box: • Ubuntu 14.04 • PHP 5.6 • HHVM • Nginx • MySQL • Postgres • Redis • NodeJS • Bower • Grunt • Gulp • Beanstalkd • Memcached • Laravel Envoy Fabric + HipChat Extension + more!
- 21. Getting Homestead Install the box: vagrant box add laravel/homestead Clone the Repository: git clone https://github.com/laravel/homestead.git Homestead
- 22. Configure Homestead Default: Hello World:
- 23. Update /etc/hosts* 192.168.10.10 hello-world.app *This step is optional
- 24. Ready to vagrant up Our code will be shared from our host machine ~/PhpstormProjects/hello-world And mapped to the vagrant machine /home/vagrant/hello-world
- 25. $ vagrant up
- 26. What now?
- 27. How to access our hello-world.app These are ports forwarded to homestead
- 28. Connect to the Database
- 29. Connect via a browser
- 30. Or use the hostname* *If you added the host to your /etc/hosts
- 31. Connect via SSH You could do this: But this is easier:
- 32. Homestead is awesome! We now have a local dev environment we can easily use, break, and restore without having to reinstall the entire operating system and developer tools. Break something?
- 33. Staking your own Homestead I like to customize homestead AND make sure I can easily update from upstream
- 34. Fork Homestead
- 37. What could customize.sh do?
- 38. You may not need customize.sh It is important to have a way to easily reproduce your development environment so that those one off changes you make are documented and two months down the road you don’t destroy & up your environment to find out you have stuff missing
- 39. Step ??? Go make something great
- 40. Tests! You've written tests all along for your app right?
- 41. PHPUnit isn’t the only option! • Behat • phpspec • Codeception
- 42. Codeception • Selenium WebDriver integration • Elements matched by name, CSS, XPath • Symfony2, Laravel4, Yii, Phalcon, Zend Framework • PageObjects and StepObjects included • BDD-style readable tests • Powered by PHPUnit • API testing: REST,SOAP,XML-RPC • Facebook API testing • Data Cleanup • HTML, XML, TAP, JSON reports • CodeCoverage and Remote CodeCoverage • Parallel Execution
- 45. TeamCity
- 46. Build Steps
- 47. All OK? Deploy!
- 48. Step Four: Hello Production
- 51. But you still have to… • Update Dependencies • Run migrations • Update Assets
- 52. Continuous Delivery Production can be updated anytime
- 53. Continuous Delivery VS Continuous Deployment
- 54. Continuous Deployment “Deploy my code every time tests pass” Continuous Delivery “We can deploy whenever we want…but we control when” Magnus Hedemark: http://puppetlabs.com/blog/continuous-delivery-vs-continuous-deployment-whats-diff
- 55. Laravel Forge “A simple way to deploy your laravel applications onto blazing fast servers”
- 56. Forge is Homestead and more in the cloud
- 57. Forge is not a server host
- 58. Forge uses your servers
- 59. Forge uses any* server *Any Internet accesible Ubuntu 14.04 x64 Server
- 60. Adding Servers To Forge
- 61. Adding a site to a server
- 62. Adding a ssh key to a server
- 63. Adding scheduled (cron) jobs
- 67. Update Server Meta Data
- 68. Adding our hello-world site
- 69. Forge can do more…
- 70. Add a WordPress Site
- 71. Ready to install
- 72. Removing WordPress Does NOT remove your WordPress Database!
- 74. Craft CMS
- 75. Uninstall Craft CMS Does NOT remove your Craft CMS Database!
- 76. Install our Git Repository
- 78. Deploy!
- 80. Deployment Log
- 82. Queue Workers
- 83. Configure / Install SSL
- 86. Quick Deploy Branch Continuous Deployment!
- 87. Recipes Recipes a bash scripts that can be run on any of your Forge servers.
- 88. Cooking up Recipes Think of recipes like our customize.sh in Homestead
- 89. All the things!
- 90. Not All The Things Some things we were doing in customize.sh we can do via Forge: • Queue Workers • Cron Jobs
- 91. Create Recipe
- 92. Run Install Bower Recipe
- 93. Forge Emails You Recipe Report
- 95. Slack Notifications You can use cURL to post to Slack channels curl -X POST --data-urlencode ‘payload= {"channel": “#devops", "username": "Forge", "text": “'"$Message"'", "icon_emoji": ":shipit:"}' https://<You>.slack.com/services/ hooks/incoming-webhook ?token=<Your-Slack-Token>
- 96. Edit our Deployment Script Now every deployment will run bower and notify our slack channel that our repo was deployed.
- 97. Hey Joe…
- 98. Been there, done that
- 99. Enable Slack
- 100. Add the Integration
- 102. Deploy!
- 103. Restarting Services Edit PHP Configuration
- 104. Delete the server
- 105. Deleting a site
- 106. Forge Circles* *Forge Plus Feature
- 107. Forge Circles* *Forge Plus Feature
- 108. Forge VS Forge Plus • Manage 5 Servers • Unlimited Servers • Forge Circles
- 109. Recap Local Development: Use Homestead Automate build tests and configure Continuous Deployment Practice Continuous Delivery if not Continuous Deployment Remote Deployment: Use Forge
- 110. Feedback! https://joind.in/talk/view/11870 Contact Info: Joe Ferguson Twitter: @Svpernova09 Email: [email protected]