I’ll say it again: do not install Laravel Tinker in production, and certainly do not use it. It’s a great tool to do work in your application, but only in test and development environments. That’s why I only install it in my require-dev section of my composer.json file.
This article will break down how I use Github Actions and Github Pages to retrieve data from an API, commit the new data to my repo, and have Github pages rebuild and use that data - all on a schedule with no hands-on interaction.
If you’re going to try to launch a startup that has a website or app as its main product, and you don’t have a technical co-founder, you should read this blog entry. It’ll save you a lot of time, headaches, and a ton of money.
As you walk down the alleyway, you feel the hairs on your neck stand up. You’re a bit scared, but you can’t exactly put your finger on why. Was that some footsteps? Did you see a shadow shift? Why is it that you know you’re in danger?
Laravel Hacker is no longer a brand. You can find my security work at MasteringLaravel.io/security
Laravel is a great framework that is pretty secure by default. However, configuration mistakes or coding errors can still leave your app open for attack. Where do you go for help?
If you want to track errors in your production Javascript (which you should), you should use a fully-baked service like BugSnag. If you can’t, there’s at least one other thing you could try: a poor man’s javascript error reporter.
When I had active membership to more than 4 Slack workspaces, I thought: wouldn’t it be nice to have a way to update all of these statuses in one fell swoop?
I’ve been working on a lot of things lately - I thought it might be nice to do a quick run down of what those are.
Conflict seems like a dirty word. After all, we don’t want to have fights at work, right? For managers, reducing conflict seems to be the best choice. But is it?
Since git does not store folders specifically (just path information), if you need an empty folder in your project that can be hard. Especially if that folder needs git to ignore any content inside of it. A community convention to solve this challenge has been the .gitkeep file. This is not part of the spec, combining that file with various .gitignore rules can solve this problem. But, there’s a better way.