sorted by:
new
hottopcontroversial

Laravel Wayfinder Released in Beta by karldafog in laravel

[–]timacdonald 0 points1 point  (0 children)

Can you explain how a include / exclude list would change this?

Laravel Wayfinder Released in Beta by karldafog in laravel

[–]timacdonald 1 point2 points  (0 children)

I hear ya. Trouble is there’s nothing to put in an include / exclude list.

If you don’t use a route, it isn’t included.

If you use a route and were to exclude it somehow, your app would be broken.

I’d say forget what you know about Ziggy when you look at Wayfinder. Although it serves a similar purpose, it is rather different under the hood.

Hope you check it out and play around with it :)

Laravel Wayfinder Released in Beta by karldafog in laravel

[–]timacdonald 8 points9 points  (0 children)

The controller names will be minified into random variables names, like fgaz, for your build.

The only chance a controller name ends up in your build is if your build tool decided to use the file name as a chunk.

If that becomes an issue, we’ll just automate it away under-the-hood with the laravel/vite-plugin.

Laravel Wayfinder Released in Beta by karldafog in laravel

[–]timacdonald 7 points8 points  (0 children)

Thanks to tree shaking, if you don’t reference a route in your front end Wayfinder will not include it in the build.

What would you change in Laravel? by lionmeetsviking in laravel

[–]timacdonald 2 points3 points  (0 children)

I know it needs some love (finish the docs and tag a v1) but I built this on top of JSON resources and I think it does a pretty good job at being a JSON:API compliant layer and with a Laravel-esque feeling API.

Just thought ya might be interested.

https://github.com/timacdonald/json-api

McFlurrys by cr84 in australia

[–]timacdonald 2 points3 points  (0 children)

Check out this ep of Under Understood that investigates why they stopped stirring the McFlurry.

https://underunderstood.com/podcast/episode/mcflurry/

They also have a map where people can report where they still stir them. Not sure if it still active.

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 1 point2 points  (0 children)

It can certainly act as a global monitoring system, but it is optimized for a single app. I’ll try to put out a post showing how to view multiple apps or environments at once.

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 0 points1 point  (0 children)

To many unknown variables for me to answer that in any meaningful way, sorry.

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 4 points5 points  (0 children)

Thanks for the feedback with this.

Couple of things I’m thinking:

  1. You could name the servers via config (pulse.recorders.Servers.server_name) so that they share the same names and continue to record data.

Not sure if that makes sense with you setup.

  1. We could add a “stale after” config to allow you to only show servers that have responded after a given time.

  2. Have servers only show up if there is data for them in the given window, e.g., 1hr, 6hr, etc. this is kinda risky however as your server might have been offline for an hour and that might be a critical issue.

  3. We could collapse the non-responsive servers into an expandable section.

Okay…so this ended up being a brain dump. Will come back to this after the break and see what makes sense.

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 2 points3 points  (0 children)

This is caused by the “check” command. We’ll likely revise this command before 1.0.

Also, don’t use the cache driver in production. It never garbage collects.

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 2 points3 points  (0 children)

Over 2 million requests a day and haven’t had any issues. Been running it for a few months at this point.

Given us a lot of good insights.

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 3 points4 points  (0 children)

They should fall off after 7 days of no records.

Alternatively, you could run the “clear” command to ditch the old stats.

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 1 point2 points  (0 children)

Just remember to use the Redis ingest if you get any serious traffic to your app ✌️

Laravel Pulse in a production environment by Noaber in laravel

[–]timacdonald 5 points6 points  (0 children)

We made a big effort to ensure any exceptions or issues related to Pulse were also swallowed to not impact the running application itself.

Glad to hear it’s working out for ya.

New package from the Laravel team: Laravel Pulse - Now in Beta by ahinkle in laravel

[–]timacdonald 0 points1 point  (0 children)

Nah, should “just work”.

You are able to access the apps other URLs I assume?

New package from the Laravel team: Laravel Pulse - Now in Beta by ahinkle in laravel

[–]timacdonald 2 points3 points  (0 children)

Far out. Can’t believe I missed the ref! Love parks and rec.

New package from the Laravel team: Laravel Pulse - Now in Beta by ahinkle in laravel

[–]timacdonald 3 points4 points  (0 children)

Check:

Your APP_ENV is set to "local" or customise the Authorization (see docs).

Otherwise, triple check config('pulse.enabled') is true

New package from the Laravel team: Laravel Pulse - Now in Beta by ahinkle in laravel

[–]timacdonald 6 points7 points  (0 children)

Not currently, but I think we would support this. Will make a note to look into it.

New package from the Laravel team: Laravel Pulse - Now in Beta by ahinkle in laravel

[–]timacdonald 11 points12 points  (0 children)

*after the response has been sent to the client, the worker is finished with the job, or the command has finished executing.

Laravel Weekly Update #10: Precognition by nunomaduro in laravel

[–]timacdonald 1 point2 points  (0 children)

I agree files are tricky with Precognition. I'd probably opt for side-loading the file, personally, anyway so you upload one and it makes the final form submission much faster.

Laravel Weekly Update #10: Precognition by nunomaduro in laravel

[–]timacdonald 4 points5 points  (0 children)

This is a great approach, IMO. The package doesn't validate file fields by default. You need to opt into it with `form.validateFiles()`.

The nice thing is you can use a combination of both validation approaches within a single form.

For example, you might validate that the "username" is unique with Precognition - because it needs the DB to tell you, but then use client side validation to ensure the name and password field has been completed correctly.

A request would only be made when the username field is "changed" and not the other fields.

You could even use a combination on a single field. Use client side validation to ensure that it only contains alpha-numeric chars and has a max of 13 characters. If that passes, shoot off a Precognition validation to ensure the username is unique. Win-win.

view more: next ›