When the whole "You're not a professional unless you use xdebug thing dropped, this talk was what my brain was searching for" https://www.youtube.com/watch?v=zKyv-IGvgGE
Also setting the timeout in my actual job classes! Seems that isn't needed when specifying a timeout on the queue worker on the CLI but is needed when your horizoning
Reached out to discord after posting here and it looks like I was missing a php artisan horizon:terminate after changing my daemon config from what I can tell
Yo #Laravel Horizon + Forge users. Do you have issues configuring your job timeouts when using Horizon? I have no issues when I just configure a regular queue worker, only when using Horizon. I tried to modify the supervisor config and restart horizon but that didn't work. ideas?
You can smash it if you like to, cuz I do what I want
How do you feel about clicking on things?
If you’re a Statamic fan, how about a little old click on the Github star?
No need to smash it or anything — this isn’t YouTube. A gentle tap should do the trick. 😊
💖 I'm sponsoring @email@example.com because… building websites has changed my life, and Statamic is making it easier to do than ever before. https://github.com/sponsors/statamic?sc=t&sp=dustinleblanc
No wonder stuff was down earlier when I was trying to migratify my blog
well geez Louise I didn't know this was happening today! https://statamic.com/blog/statamic-3-launch-announcement
The Laravel community also gives you the feeling that pretty much anyone can use the tools and build something successful. There is definitely some magic in here that just doesn't exist in the other communities I've traveled in during my professional life.
I've been doing Laravel on the side for a few years now, and I'm still not an expert, but I've been working on a SaaS product with my friend Lauren, something that would not have been possible without Laravel.
When I discovered Laravel, the similarities to Rails allowed me to Voltron together my Rails knowledge with the years of practical real world experience I now had with PHP, I no longer had to keep investing in two entirely different stacks.
I could consult for years with JUST my Drupal skills and make damn good money building websites for people until I can no longer type or program for one reason or another.
Problem was, I couldn't really work on my own ideas and just create something myself.
For a long time I was sort of doing double duty, trying to get experience on rails projects so I could move the direction of custom apps. Its just a different experience from building *websites* for people using a popular CMS. The tools are optimized for site owners, not devs.
When I started web-devving around 2012/2013, I got into rails, then my first web gig was doing Drupal and that stuck for a few years. I wanted so desperately to get back to the dev-focused framework experience I loved from my taste of rails, but had invested heavily in PHP
Initially, @firstname.lastname@example.org was inspired by Rails.
But these days, it feels like it's *Laravel* that's influencing the rest of the web dev world.
Lead Technical Support Engineer at Pantheon, Co-Maintainer of Lando, passionate optimist and annoying conceptual
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!