Tray2

All filtering and sorting should be done in the database. It is faster and better at it than any php code you will ever write.

Where do you add the user to the database? If there are no users in the database which it isn't when you refresh the database it will fail the login.

I can recommend this course for that

https://laraveldocker.com/

You can do this.

$model = new Model();
$model->field = $request->field
$model->field2 = $value;
$model->save();

Or this

$data = $request->validate($rules);
$data['another_field'] = $valiue;
Model::create($data);

You can do this.

$model = new Model();
$model->field = $request->field
$model->field2 = $value;
$model->save();

Or this

$data = $request->validate($rules);
$data['another_field'] = $valiue;
Model::create($data);

I would most likely build everything in Laravel and use the artisan console commands for doing the console stuff

Ok, that is a valid reason, You probably should update those videos ;)

Why use 5.8 for a new project?

I would most likely build everything in Laravel and use the artisan console commands for doing the console stuff

You can add the throttle middleware to your routes

https://laravel.com/docs/8.x/routing#rate-limiting

Have you checked out Gallery?

http://galleryproject.org/

@binggle that might seem like a good option but that isn't always the case.

With the wrong indexes you might make it harder for the parser to generate the best execution plan.

Are you running then in the correct order?

You need to run the Article migration first then the article tag one.

You can use signed url for that.

https://laravel.com/docs/8.x/urls#signed-urls

That is up to you but the thought behind TDD is not to write any code until you have a failing test.

Just use a simple where

->where([ 
		['model_type',  '=',  'App\Model\Post' ],
		[ 'model_id', '=', 1]
])

Why are you using a json column to begin with?

They will only make your life harder.

Create a proper database model instead it will be much faster and it won't give you the headache of doing crud in a json field..

What happens if you change this line in your validations?

 'files.*' => ['required']

to

 'file' => ['required']

Have you set the enctype in your view?

enctype="multipart/form-data"

Try adding an index to the created_at field and you should see an performance increase.

$table->index('created_at');

https://laravel.com/docs/8.x/migrations#available-index-types

Just use a simple where

->where([ 
		['model_type',  '=',  'App\Model\Post' ],
		[ 'model_id', '=', 1]
])

So you only want records that has an aquantity that is bigger than bquentity?

Then use a where

->where('aquantity', '>', 'bquantity')

Pivot tables are great but not for what you are trying to achieve.

Create one table called user_properties or similar then you have three fields

• user_id
• property
• value

Your records would look something like this

1 |   language  | English
1  | language | Danish
1   |hobby | Paragliding 

You can also use chunking so that you send maybe 4000 every itteration.

Are you running then in the correct order?

You need to run the Article migration first then the article tag one.

You can add the throttle middleware to your routes

https://laravel.com/docs/8.x/routing#rate-limiting

Read up on eager loading

https://laravel.com/docs/8.x/eloquent-relationships#eager-loading

You pass it an email and expect it to be null?

Does that class exist? Have you imported it properly? Does it have the correct namespace?

You can use the withSum() and withCount for that

https://laravel.com/api/8.x/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.html#method_withCount

https://laravel.com/api/8.x/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.html#method_withSum

I suggest you use laravel breeze or laravel jetstream instead of building your own login,

The solutions for Laravel 5 will most likely work in Laravel 8 as well

Try adding an index to the created_at field and you should see an performance increase.

$table->index('created_at');

https://laravel.com/docs/8.x/migrations#available-index-types

Why can't you just use the id?

Check out this post

https://blog.maqe.com/solved-eloquent-doesnt-support-composite-primary-keys-62b740120f

Eleoquent doesn't support it but it seems that the query builder does so I suggest you use it.

Do you have the correct permissions and owner on the files and directories?

If you haven't already I suggest you install a proper lamp or lemp instead of using serve.

https://www.howtoforge.com/tutorial/install-laravel-on-ubuntu-for-apache/

https://www.howtoforge.com/tutorial/ubuntu-laravel-php-nginx/

Or even using docker

https://www.howtoforge.com/dockerizing-laravel-with-nginx-mysql-and-docker-compose/

What doesn't work?

What error messages do you get? What do you expect to see?

What happens if you do

foreach($model as $transaction => $value) {
	$value::selectRaw() //and so on
}

You can create a models directory in your tests directory and add it to autoload dev in your composer.json file

  "autoload-dev": {
      "psr-4": {
        "App\Models\": "tests/laravel/Models"
      }
    },

Then you can use eloquent in your code,

You probably use database migrations in your tests. Then the migrations is rolled back.

What OS are you running?

Are you sure you have the word sulaimani in one of those fields in the database?

You can use signed url for that.

https://laravel.com/docs/8.x/urls#signed-urls

Never use 777 as a permission. With that permission anyone can crash your site by running a simple rm -rf ./

Why do you create a OS user when creating an application user?

One option is to add the created user to the www-data group however this gives the user pretty much full access to everything in your web root which is really bad.

I say rethink your strategy here and give some really compelling reasons to do it that way.

It's basically just typed javascript that needs to be compiled into regular javascript. It has its benefits but unless you want javascript typed it's really not that necessary imho.

You probably use database migrations in your tests. Then the migrations is rolled back.

Are you using Orchestra/Testbench?

If so check your TestCase.php file and make sure you have the correct config there.

It might look something like this

  protected function getEnvironmentSetUp($app): void
  {
      $app['config']->set('database.default', 'mysql');
      $app['config']->set('database.connections.mysql', [
          'driver'   => 'mysql',
          'database' => 'mediabase',
          'prefix'   => '',
          'username' => 'root',
          'host' => '127.0.0.1'
      ]);
  }

You could probably get away with using exclude_if on the rules after,

https://laravel.com/docs/8.x/validation#skipping-validation-when-fields-have-certain-values

Are you running phpunit from the project root?

Do you have SQLite installed?

Have you defined a connection in any of your models?

You could probably get away with using exclude_if on the rules after,

https://laravel.com/docs/8.x/validation#skipping-validation-when-fields-have-certain-values

Of course not, You need to order it when you fetch it from the database not after it's already fetched,

Of course not, You need to order it when you fetch it from the database not after it's already fetched,