bugsysha

Doesn't debugbar tell you what initiated those queries? Exact file and line?

Initial response is stored in some array on the React component. You remember what the next URL is from initial paginated response and when you load more, then just append to that same array you have on the React component new data you got from response. Nothing complicated.

On this site there is a link for GitHub actions tutorial with Laravel. Also based on that video it looks like this course will be nice for that topic. Maybe that is enough for you to figure out the rest. Give it a try.

How did you forget to say that you are running it in Sail? Have you tried everything from the docs regarded to Sail and Dusk? https://laravel.com/docs/8.x/sail#laravel-dusk

And what happens in the browser when you go to that URL? http://0.0.0.0:88/

Does it work if you run php artisan serve?

Laravel is not the best choice for shared hosting. Laravel doesn't abuse CPU so if it is related to your Laravel site it is caused by your code or some package you are using. You should profile your Laravel app locally with XDebug and figure out if there are any issues.

☝🏽

Nobody is blaming you. It is just no useful and hard to figure out from given info. That is just another thing we need to master in order to communicate well with other developers.

@xtremer360

This way in case I'm working on multiple apps at the same time I can have their database names to be different.

I shutdown the current "sail" and start a different/new one. That way I never have to think about which port I need to use to access the database or any of services running in containers.

Yeah, that will do also.

But I was wondering, if I place a component inside a if/else or can. Will anyone be able to use/tinker with them, or will it only work if it's displayed?

It will only work if displayed/rendered.

I think that most developers use route() helper function, but I like action() more. If I'm sole developer I use actions. If I join the team with existing project then I use what was most used in that project.

If you have a huge project I advise that you use full path (literal URI as you call it) cause it will make life easier for everyone since if you have more routes with similar names you will have problems tracking them down.

Depends on their use. If you need all of them all the time then mix them and set not to expire that often. If you need only few of them then leave them separated.

Ex: i want to get events which has category slug "entertainment" . How to do that dynamically?

Product::with('Categories')->whereHas('categories', function ($query) use ($categoryName) {
  $query->where('category_name', $categoryName);
})->orderBy('id','DESC')->get();

if i use whereHas it will scan full table. will it affect the performance if my table has 10000 records for each category?

Affect performance compared to what? More complex queries are slower, but there is no faster way to do it if that is what you are asking.

But I was wondering, if I place a component inside a if/else or can. Will anyone be able to use/tinker with them, or will it only work if it's displayed?

It will only work if displayed/rendered.

Yeah I was trying to be funny so I don't insult you. The reason why nobody replied besides me is cause your description of a problem is very confusing and there is no real question there.

but this will not happen

What code did you write to make this happen?

I don't see autofocus attribute anywhere in your code. What have you tried?

Visit your site page and click on redirects and add the rule.

https://forge.laravel.com/servers/123456/sites/654321#/redirect-rules

What do you consider as "Laravel basic authentication"? Cause JWT is not basic auth for Laravel.

My request from Frontend

Your "frontend" request looks like backend request.

Thank you!

You are very welcome.

What is the problem?

You need to tell us what is the problem, not the other way around.

Have you checked these videos?

If you have 10 managers then track order count (or use ID) and use % operator. You don't need a package for such a simple thing.

Post a screenshot of your TablePlus connection.

On this site there is a link for GitHub actions tutorial with Laravel. Also based on that video it looks like this course will be nice for that topic. Maybe that is enough for you to figure out the rest. Give it a try.

Maybe you should just create a simple middleware that ensures your clients meet the required criteria to access the pages.

Does anyone have a good resource of modern Laravel tutorials please, preferably if they are building a project too.

Have you watched Let's Build A Forum with Laravel and TDD?

I know, just kidding ;)

Is it a good practice to add custom verbs to Policies?

Yes. I usually try to break down those verbs since they tend to be same as some other rule from basic verbs. But when that is not the case then I create custom ones.

Nope :D

Show your database structure and relationships.

Show the code. Error can be due to simple typo to who knows what reason.

$response = \Illuminate\Support\Facades\Http::get('google.com');
$size = strlen($response->body());

return redirect()->to('/something#1234');

I mentioned to @godzilaravel yesterday that the only option here is to put the JSON content in a Blob, allow the original types to be maintained whenever there is an image in the request.

@tykus thanks for letting us know.

@godzilaravel if I understand the situation correctly, why don't you listen to given advice, but instead you create another topic?

@godzilaravel I don't see anything wrong there. Did you try using full syntax axios.patch(url[, data[, config]])?

Thanks.

In my opinion it is a lazy developer way. Proper way would be to implement that into your codebase. So if it ever happens for you to switch to some database that does not support that feature you will not have a thing to worry about. I really don't see why the database should contain any business rules and everything should be explicit in the code.

return redirect()->to('/something#1234');

Are you using enctype=multipart/form-data?

With Vapor I wouldn't think about anything else. Reason for it is I've tried a bunch of services for hosting Laravel apps and none of them was as seamless as Forge. I'm pretty sure same thing goes for Vapor.

I do not have it installed locally cause I'm using docker, but you can check nginx and php logs. They should be somewhere in /usr/local/var/log.

Sure.

1. It causes problems with testing.
2. If you type hint that class in some other class that is resolved out of the container you increase framework boot time, and that might happen on every request.
3. If you have multiple instances of that class you will query the database each time but you probably need to do it only once.
4. Your database calls should be peripheral and not coupled to core business domain logic.
5. What if the business rules change and you need to fetch the data at later stage, you would have to do it twice or to move it. Colleague of mine who was supposed to be promoted to lead position over me made this mistake and I've nagged him for weeks about it and he ignored me until the business logic change was requested which prove that I was right about the concerns of having that stuff inside of constructor.
6. Query can fail.
7. Constructor shouldn't do any work.
8. When the class is extended it will do additional queries.

And so on... I'm sure that the internet is full of reasons why you shouldn't do it in the constructor so just Google a bit cause it is a bit fat no-no.

Hope this was clear enough and I didn't just confuse you further.

Any suggestions?

Reboot.

I have a service class VideosHandler in which constructor I get database records for further usage in this service class.

You should avoid doing that. Numerous problems can happen from that kind of implementation. Move that outside of the __construct method and do not call it on object construction.

Then when should we use saveOrFail()??

I usually do not use it. From those *OrFail methods I think I only use firstOrFail.

$this->actingAs() is just setting the user to current guard. Auth::login() is updating the session, remembering the user by setting the token and cookie, and it is firing the events and setting the user to the guard.

For tests you should only use $this->actingAs() or $this->be().

Also, you should not assert that the resource is not found, you should assert that it is forbidden to access that resource.

Could you please elaborate on this?

Sure. There is nothing smart about it. If you use single database and that record exists then you found it but just do not allow the user to see it since that specific user is not the "owner" of that record. If you are using multiple databases and you try to access a record which does not exist in that database then it is OK to respond with not found.

From your code I would say that you have the first scenario and you should send forbidden response.