by Devin Yang
(This article was automatically translated.)

Published - 3 years ago ( Updated - 3 years ago )

Livewire is a full-stack framework for the Laravel framework.
It was the first time I wrote code, and he was probably the one who was able to write and marvel at the magic.
My colleague also marveled while writing after being pushed by me.
When I first learned Vue, I was not so surprised by him.

This article introduces how fun Livewire is through the simple operation I recorded.
Imagine that components can be reused, the back-end PHP content changes, the front-end screen does not need to be completely reloaded,
PHP variables can be directly bound to the front-end screen,

There are many more The powerful functions are not introduced in this film, so I leave it to everyone to study by themselves.

Here, I share how to upload files with Livewire through this short video. This is not a teaching video, but I believe that everyone can Google the relevant instructions for the code in the video.
Actually, there are not many things, because it is really too simple:p

https://youtu.be/JPiFGYLn5po

 

 



 

Tags: laravel laravel livewire

Devin Yang

Feel free to ask me, if you don't get it.:)

No Comment

Post your comment

Login is required to leave comments

Similar Stories


docker,laravel

It's super easy to build a Lravel development environment with Docker

Are you ready for the Laravel 5.5 system environment? laravel/framework 5.5.x-dev requires php >=7.0 -> your PHP version (5.6.30) does not satisfy that requirement. This article describes how to create a Laravel development environment using Docker. With the simple to explosive D-Laravel simple bash, Don't say that I can't set up a Laravel development environment.

Laravel,artisan

About the operation of --env in Laravel's artisan

This article uses Laravel 9.40.1 for operation. I believe many people know the usage of --env, but I still provide some information for Laravel beginners. In the artisan command, we can use --env to specify different .env files, so that under different subdomains, I can use different environments or even different databases. You should have also noticed that this site uses a multilingual environment, do you write two sets? Of course not, basically I created multiple .env in the same Project.