William Rodriguez

Full-Stack Developer @honorlock. Freed by #laravel years ago and have never stopped learning!

[William Rodriguez @WillRodRican]

@saviomartin7 👋

[William Rodriguez @WillRodRican]

@Alpine_JS @calebporzio - It looks like the ticket is purchased through Github sponsorship. How would I buy multiple tickets for my team without having them individually sponsor through Github?

[William Rodriguez @WillRodRican]

@themsaid Great! I will checkout it out. We are currently on 8.27 so going to 8.33 will be a non-issue.

Thank you so much @themsaid for responding and the help!

[William Rodriguez @WillRodRican]

@themsaid Hoping for some Laravel queue magicians: I have a Laravel project that splits queries between a reader and writer RDS instance. I have several supervisor workers for the different SQS queues. My expectation is that each time the worker processes a job... cont.

[William Rodriguez @WillRodRican]

@themsaid I thought this was the case... I changed the supervisor conf file to `queue:listen` instead of `queue:work` so that it would disconnect and reconnect on each job.

Is there a better way to handle this? We want the worker to stay connected, but reset its connection to the reader.

[William Rodriguez @WillRodRican]

@themsaid Yes, "sticky" is set to true. My understanding is that when it is set to true, it will move to the writer when it needs to write, and stay there for the rest of the request.

[William Rodriguez @WillRodRican]

subsequent queue jobs are only being thrown at the writer and never using the reader.

Is there something that I am missing? Is there a way to force the job to always start with the reader?

[William Rodriguez @WillRodRican]

when it starts working, it queries against the reader, and then when it writes, it pops over to the writer and stays there. But when a new job comes in, it SHOULD start again at the reader and then pop over to the writer when it needs to. But what I am seeing is that all.. cont.

[William Rodriguez @WillRodRican]

@flicknelson These look excellent! I’m hoping for a round 3.... thanks for the response!

[William Rodriguez @WillRodRican]

@bobbybouwmann @stefanbauerme Bought!

[Michael Dyrynda @michaeldyrynda]

To celebrate the release of @spatie_be's new debugging tool, Ray, I'm giving away two licenses! All you need to do is retweet this tweet to be in for a chance to win. Competition open until January 12 at 10am ET.

[William Rodriguez @WillRodRican]

@daviderognoni @Alpine_JS @tailwindcss @tailwindui hits the mark closer than anything else.

[William Rodriguez @WillRodRican]

Last week I helped someone struggling with building a modal using @Alpine_JS. Before then, since AlpineJS modal tutorials already existed, I didn’t think the world needed another one. Seeing the struggle first hand, maybe I can offer a new perspective.

https://t.co/EmRwtYWrTQ

[William Rodriguez @WillRodRican]

Just bought 2 @beyondcode apps I have been eyeing for a while: @Tinkerwellapp & #helo. Already started playing with them and love how easy they are to use. Solid, simple products!

[William Rodriguez @WillRodRican]

@JackEllis @laravelphp Agreed. I will need to consider the pro’s and con’s of using lambdas vs dedicated instances to process the videos. Thanks for the response!

[William Rodriguez @WillRodRican]

@laravelphp @JackEllis I'm moving an app onto Laravel Vapor that requires ffmpeg. Is there a way to use Lambda Layers in order to use ffmpeg through the vapor lambdas?

Should I just have a dedicated EC2 to process the ffmpeg jobs instead? Thanks for any advice!

[William Rodriguez @WillRodRican]

@owenconti @laravelphp @JackEllis I appreciate the quick response! To be honest, I didn’t even search for “Layers” in the vapor docs. I’m trying it out now. Thanks!

[William Rodriguez @WillRodRican]

@olark @OlarkSupport - It doesn't look like this service was ready for general availability. Ever since we moved a portion of our chat service to Olark, we have experience nothing but problems. A very promising product brought down by poor execution. 😞

[William Rodriguez @WillRodRican]

We are aggressively looking for top senior @laravelphp developers. We operate on the TALL stack. We are on the verge of moving to Vapor and need someone who can kill it with expanding our event-driven architecture.

We pay top dollar for top engineers. PM me for more information.

[William Rodriguez @WillRodRican]

@laraveljobs We are hiring a senior developer, not a CTO... either way, we have a lot of fun!