Laravel is a great framework to use for web applications but what if you need to do more? What if you need to process data that would take longer than an HTTP request would allow? Come learn how to harness the power of the console in your Laravel applications to do various tasks such as caching data from 3rd party APIs, expire old content from S3 or other data store, and batch process huge data sets without users having to wait for results. You can even automate tasks such as backing up your remote databases before you run migrations with artisan commands. We'll cover creating basic artisan console commands, adding options and passing input, setting up cron jobs and scheduling our console commands to run at specific times, and how you can utilize 3rd party APIs to create fun automated message processing for social media networks.

1. Console Apps:
php artisan forthe:win
Joe Ferguson

2. Who Am I?
Joe Ferguson
PHP Developer
Engineer @ Aol.
Twitter: @JoePFerguson
Organizer of @MemphisPHP
OSMI Board Member
@NomadPHP Lightning Talks
Passionate about Community

3. For Further Reading
https://leanpub.com/signalingphp

4. Console Apps?!

5. Shouldn’t we be doing
this in __________ ?

6. Symfony Console
http://symfony.com/doc/current/components/console.html

7. Symfony Console

8. Artisan Console

9. Laravel Artisan
https://laravel.com/docs/5.3/artisan

10. Artisan Commands

11. Create a new Command

12. Create a new Command

13. app/Console/Kernel.php

14. BasicCommand.php

15. Signature

16. Description

17. Constructor

18. Handle The Command

19. Running our Command

20. Output Some Text

21. Output Some Text

22. Output Warning Text

23. Output Warning Text

24. Output Error Text

25. Output Error Text

26. How do we test the
Command?

27. BasicCommandTest

28. BasicCommandTest

29. Adding Checks

30. BasicCommandTest

31. Database Backup

32. Create
DatabaseBackupCommand

33. app/Console/Commands

34. Don’t forget Kernel.php!

35. app/Console/Commands

36. Look for our Command

37. Write our handle()

38. Write our handle()

39. But we use RDS!

40. Command SnapshotRds

41. Write our __construct()

42. Write our handle()

43. Running Our Command

44. AWS Console

45. I can do that automatically…

46. What if you don’t use RDS?

47. spatie/laravel-backup

48. AWS S3 File Storage

49. Configure
S3ExampleCommand

50. List items in a bucket

51. List items in a bucket

52. Get an object by Key

53. Get an object by Key

54. Deleting old assets

55. Deleting old assets

56. Cache Data From APIs

57. Configure
CacheApiDataCommand

58. dms/meetup-api-client

59. meetupConnect()

60. handle()

61. Command Arguments

62. Default in $signature

63. We need a way to
persist the API data…

64. Database to the rescue!

65. Empty Migration

66. Event Details

67. Migration up()

68. Migration down()

69. Run Migrations

70. Create Meetup Model

71. Process the events

72. Check the database

73. Now we can pull events
from our database

74. Elasticsearch

75. 20 Events is a pretty
small data set

76. GetAllMeetups*
*not all meetups

77. GetAllMeetups
Command

78. A larger meetup group

79. Update the handle()

80. Run our command

81. Check the database

82. Batch Process Large
Data Sets

83. Configure
BatchProcessCommand

84. handle()
BatchProcessCommand

85. Running meetup:expire

86. Schedule Our
Commands

87. artisan schedule:run

88. Scheduling Commands
app/Console/Kernel.php

89. Scheduling Commands

90. Real World Twitter
Demo

91. Questions?

92. Feedback!
https://joind.in/talk/2045d
Joe Ferguson
Twitter: @JoePFerguson
Email: joe@joeferguson.me
Freenode: joepferguson
Contact Info: