Now, let’s see article of laravel 8 livewire crud example. This tutorial will give you simple example of laravel 8 livewire crud with jetstream & tailwind css. i would like to show you laravel 8 livewire crud with modal. We will look at example of laravel 8 jetstream livewire crud application example.

In this example i will show you step by step laravel 8 livewire crud app with modal tailwind css.

Laravel 8 jetstream designed by Tailwind CSS and they provide auth using livewire and Inertia. i will show you how to create module with livewire on default jetstream auth in laravel 8.

Here, bellow i written step by step, so you can easily start simple post master with your existing step up of laravel 8 jetstream auth with tailwind css. you just need to follow few bellow step and you will get layout as like bellow:

Preview:

List View:

Create View:

Update View:

Step 1: Install Laravel 8

here, we need to install laravel 8 application using composer command.

composer create-project --prefer-dist laravel/laravel blog

Step 2: Create Auth with Jetstream Livewire

Now, in this step, we need to use composer command to install jetstream, so let’s run bellow command and install bellow library.

composer require laravel/jetstream

now, we need to create authentication using bellow command. you can create basic login, register and email verification. if you want to create team management then you have to pass addition parameter. you can see bellow commands:

php artisan jetstream:install livewire

Now, let’s node js package:

npm install

let’s run package:

npm run dev

now, we need to run migration command to create database table:

php artisan migrate

Step 3: Create Migration and Model

Here, we need create database migration for files table and also we will create model for files table.

php artisan make:migration create_posts_table

Migration:

<?php
 
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;
 
class CreatePostsTable extends Migration
{
 /**
 * Run the migrations.
 *
 * @return void
 */
 public function up()
 {
 Schema::create('posts', function (Blueprint $table) {
 $table->id();
 $table->string('title');
 $table->text('body');
 $table->timestamps();
 });
 }
 
 /**
 * Reverse the migrations.
 *
 * @return void
 */
 public function down()
 {
 Schema::dropIfExists('posts');
 }
}

php artisan migrate

now we will create Post model by using following command:

php artisan make:model Post

App/Models/Post.php

<?php
 
namespace App\Models;
 
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;
 
class Post extends Model
{
 use HasFactory;
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 protected $fillable = [
 'title', 'body'
 ];
}

Step 3: Create Post Component

Now here we will create livewire component using their command. so run bellow command to create post crud application component.

php artisan make:livewire posts

Now they created fies on both path:

app/Http/Livewire/Posts.php
resources/views/livewire/posts.blade.php

Step 4: Update Component File

Here, we will write render(), create(), openModal(), closeModal(), resetInputFields(), store(), edit() and delete() method for our crud app.

So, let, update following file.

app/Http/Livewire/Post.php

<?php
 
namespace App\Http\Livewire;
 
use Livewire\Component;
use App\Models\Post;
 
class Posts extends Component
{
 public $posts, $title, $body, $post_id;
 public $isOpen = 0;
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 public function render()
 {
 $this->posts = Post::all();
 return view('livewire.posts');
 }
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 public function create()
 {
 $this->resetInputFields();
 $this->openModal();
 }
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 public function openModal()
 {
 $this->isOpen = true;
 }
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 public function closeModal()
 {
 $this->isOpen = false;
 }
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 private function resetInputFields(){
 $this->title = '';
 $this->body = '';
 $this->post_id = '';
 }
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 public function store()
 {
 $this->validate([
 'title' => 'required',
 'body' => 'required',
 ]);
 
 Post::updateOrCreate(['id' => $this->post_id], [
 'title' => $this->title,
 'body' => $this->body
 ]);
 
 session()->flash('message', 
 $this->post_id ? 'Post Updated Successfully.' : 'Post Created Successfully.');
 
 $this->closeModal();
 $this->resetInputFields();
 }
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 public function edit($id)
 {
 $post = Post::findOrFail($id);
 $this->post_id = $id;
 $this->title = $post->title;
 $this->body = $post->body;
 
 $this->openModal();
 }
 
 /**
 * The attributes that are mass assignable.
 *
 * @var array
 */
 public function delete($id)
 {
 Post::find($id)->delete();
 session()->flash('message', 'Post Deleted Successfully.');
 }
}

Step 5: Update Blade Files

Here, we will update following list of files for our listing page, create page.

So, let’s update all the files as bellow:

resources/views/livewire/posts.blade.php

<x-slot name="header">
 <h2 class="font-semibold text-xl text-gray-800 leading-tight">
 Manage Posts (Laravel 8 Livewire CRUD with Jetstream & Tailwind CSS - ItSolutionStuff.com)
 </h2>
</x-slot>
<div class="py-12">
 <div class="max-w-7xl mx-auto sm:px-6 lg:px-8">
 <div class="bg-white overflow-hidden shadow-xl sm:rounded-lg px-4 py-4">
 @if (session()->has('message'))
 <div class="bg-teal-100 border-t-4 border-teal-500 rounded-b text-teal-900 px-4 py-3 shadow-md my-3" role="alert">
 <div class="flex">
 <div>
 <p class="text-sm"></p>
 </div>
 </div>
 </div>
 @endif
 <button wire:click="create()" class="bg-blue-500 hover:bg-blue-700 text-white font-bold py-2 px-4 rounded my-3">Create New Post</button>
 @if($isOpen)
 @include('livewire.create')
 @endif
 <table class="table-fixed w-full">
 <thead>
 <tr class="bg-gray-100">
 <th class="px-4 py-2 w-20">No.</th>
 <th class="px-4 py-2">Title</th>
 <th class="px-4 py-2">Body</th>
 <th class="px-4 py-2">Action</th>
 </tr>
 </thead>
 <tbody>
 @foreach($posts as $post)
 <tr>
 <td class="border px-4 py-2"></td>
 <td class="border px-4 py-2"></td>
 <td class="border px-4 py-2"></td>
 <td class="border px-4 py-2">
 <button wire:click="edit()" class="bg-blue-500 hover:bg-blue-700 text-white font-bold py-2 px-4 rounded">Edit</button>
 <button wire:click="delete()" class="bg-red-500 hover:bg-red-700 text-white font-bold py-2 px-4 rounded">Delete</button>
 </td>
 </tr>
 @endforeach
 </tbody>
 </table>
 </div>
 </div>
</div>

resources/views/livewire/create.blade.php

<div class="fixed z-10 inset-0 overflow-y-auto ease-out duration-400">
 <div class="flex items-end justify-center min-h-screen pt-4 px-4 pb-20 text-center sm:block sm:p-0">
 
 <div class="fixed inset-0 transition-opacity">
 <div class="absolute inset-0 bg-gray-500 opacity-75"></div>
 </div>
 
 <!-- This element is to trick the browser into centering the modal contents. -->
 <span class="hidden sm:inline-block sm:align-middle sm:h-screen"></span>​
 
 <div class="inline-block align-bottom bg-white rounded-lg text-left overflow-hidden shadow-xl transform transition-all sm:my-8 sm:align-middle sm:max-w-lg sm:w-full" role="dialog" aria-modal="true" aria-labelledby="modal-headline">
 <form>
 <div class="bg-white px-4 pt-5 pb-4 sm:p-6 sm:pb-4">
 <div class="">
 <div class="mb-4">
 <label for="exampleFormControlInput1" class="block text-gray-700 text-sm font-bold mb-2">Title:</label>
 <input type="text" class="shadow appearance-none border rounded w-full py-2 px-3 text-gray-700 leading-tight focus:outline-none focus:shadow-outline" id="exampleFormControlInput1" placeholder="Enter Title" wire:model="title">
 @error('title') <span class="text-red-500"></span>@enderror
 </div>
 <div class="mb-4">
 <label for="exampleFormControlInput2" class="block text-gray-700 text-sm font-bold mb-2">Body:</label>
 <textarea class="shadow appearance-none border rounded w-full py-2 px-3 text-gray-700 leading-tight focus:outline-none focus:shadow-outline" id="exampleFormControlInput2" wire:model="body" placeholder="Enter Body"></textarea>
 @error('body') <span class="text-red-500"></span>@enderror
 </div>
 </div>
 </div>
 
 <div class="bg-gray-50 px-4 py-3 sm:px-6 sm:flex sm:flex-row-reverse">
 <span class="flex w-full rounded-md shadow-sm sm:ml-3 sm:w-auto">
 <button wire:click.prevent="store()" type="button" class="inline-flex justify-center w-full rounded-md border border-transparent px-4 py-2 bg-green-600 text-base leading-6 font-medium text-white shadow-sm hover:bg-green-500 focus:outline-none focus:border-green-700 focus:shadow-outline-green transition ease-in-out duration-150 sm:text-sm sm:leading-5">
 Save
 </button>
 </span>
 <span class="mt-3 flex w-full rounded-md shadow-sm sm:mt-0 sm:w-auto">
 
 <button wire:click="closeModal()" type="button" class="inline-flex justify-center w-full rounded-md border border-gray-300 px-4 py-2 bg-white text-base leading-6 font-medium text-gray-700 shadow-sm hover:text-gray-500 focus:outline-none focus:border-blue-300 focus:shadow-outline-blue transition ease-in-out duration-150 sm:text-sm sm:leading-5">
 Cancel
 </button>
 </span>
 </form>
 </div>
 
 </div>
 </div>
</div>

Step 6: Add Route

In third step, we will create routes for multiple file upload. so create two route with GET and POST route example.

routes/web.php

<?php
 
use Illuminate\Support\Facades\Route;
 
use App\Http\Livewire\Posts;
 
/*
|--------------------------------------------------------------------------
| Web Routes
|--------------------------------------------------------------------------
|
| Here is where you can register web routes for your application. These
| routes are loaded by the RouteServiceProvider within a group which
| contains the "web" middleware group. Now create something great!
|
*/
 
Route::get('post', Posts::class);

Now you can run your application by bellow command:

php artisan serve

now you can run app and login as user, then you can open bellow url:

//localhost:8000/post

now it’s works…

I hope it can help you…

Established Field Guide favorite IFTTT (If This Then That) has a new pro subscription, giving you more options and more features than before for $10 a month (though you can actually set your own price for the first year). It’s something for power users to consider adding to their digital subscriptions.

For the completely uninitiated, IFTTT basically connects services together—Spotify and Slack, Gmail and Dropbox, Instagram and Pocket—so you can have triggers in one service lead to actions in another service. A simple IFTTT applet could be getting an email every time there’s a public tweet tagged with a specific location.

Here’s everything you can do with the new Pro subscription.

In addition to executing applets faster, the new IFTTT Pro plan lets you put together multiple actions and multiple triggers in the same applet, create routines with multiple steps, and introduce queries and conditional logic. That means applets can be much more complex, if you need them to be. Those on a free IFTTT plan will be limited to three applets in the future.

Once you’ve signed up to access the Pro features, you can start building your applet by clicking Create from the main screen on the web. You begin with two basic If This and Then That blocks, and you can use the Add buttons to pick your services: When you click into a service, a choice of different triggers or actions appears.

Select Feedly as your trigger, for instance, and the available triggers include a new article saved for later, a new highlight, or a new article in a board. If you choose a service that you haven’t previously connected to IFTTT, then you’re going to need to provide your login credentials and allow access as well.

What’s new with a Pro subscription are the Plus buttons underneath the If This trigger and the Then That action. Click on these buttons and you can add queries to refine your applet and multiple actions at the end of it. With a little bit of experimentation you should be able to work out what you can do with these extra fields.

Queries are intended to enable you to add more context and information to an applet, which then affects whether or not it gets triggered, and again you’ve got a host of different options and services to pick from—example queries would be the current weather forecast or the current price of electricity.

For example, it can be useful to apply a filter so an IFTTT only runs at a specific time of day or on a specific day of the week. Or, you might want to have an applet that’s triggered by a Google Calendar event, but only with a certain keyword in the title. These are the sorts of granular controls you can apply as you build up your applet.

Some technical and coding know-how is required to get the most out of the query and filter features, but it’s not difficult to pick up: IFTTT has put together a helpful guide that will take you through the time of day filter, and several others, here. Once you’ve got a grasp of the basic syntax and structure, you can adapt it for your own needs.

As you close out the applet creation process, you might be asked to add some specifics about how the action is carried out, depending on what you’re building. A lot of the triggers that IFTTT supports will come with so-called ‘ingredients,’ or types of data that are mined from the connected service.

Say you’re using an applet to add all of your finely honed tweets to a Google Sheet. As you build the applet, you can choose which of the tweet’s ingredients are included: the time and date it was created, the username it was tweeted from, a URL leading back to the tweet, the text of the actual tweet itself, and the tweet embed code. All of these elements can be included or excluded and ordered as required.

All of these settings can be configured at any time through your IFTTT dashboard, and all of your applets can be turned on or off whenever you like. You can also manage your account through the IFTTT apps for Android and iOS, though you can’t dig into the construction of your applets in quite as much detail as you can through a web browser—when you’re creating applets, it’s best to do it in a desktop web browser.

The easiest way to understand how IFTTT and IFTTT Pro works is just to dive in and work through some examples. IFTTT provides a few examples itself, so you can see how the queries and filter code in particular can be used. You can, for example, send an alert when you hit your daily distance goal in the Fitbit app—but disable the alert on certain days, and change the wording when the weather isn’t good.

You can also use IFTTT to turn on a SmartThings lightbulb based on the amount of available natural light—data obtained through a query run through a Tempest Weather System. When your custom brightness threshold is met, the lights turn on. (IFTTT works with a bunch of other smart home platforms as well.)

Another official example from IFTTT sets an applet to run once a day, using Date & Time as the trigger and Weather Underground as a weather forecast source. If the outlook is good, you’ll get a reminder to go for a run added to your Google Calendar, which is the main action in the applet.

Even if you don’t go deep into the query and filter coding aspects of IFTTT Pro, being able to run as many applets as you want with multiple actions might make the subscription worth your while. It really depends whether you need more from the apps and services that you use every day—and whether IFTTT has deep enough hooks into them to give you more functionality and features than you get by default.

Let’s build a datatables component that allows a person to search, filter, sort and manipulate the query string. This component will demonstrate the power of Livewire, as building a datatables component the traditional way would require a significant amount of JavaScript.

View the source code for this episode on GitHub.

Published on Sep 16th, 2020.

POTD: A-10 Thunderbolt II with GAU-8 Avenger 30mm Rotary Cannon

Posted 5 mins ago in Defense, Photo Of The Day with No Comments
Tags: a-10, GAU-8, Thunderbolt

Photo Of The Day

– Flying above is a U.S. Air Force

A-10 Thunderbolt II

assigned to the 51st Fighter Wing during a RED FLAG-Alaska over the Yukon Training Area in Alaska in 2019. As you may know, the A-10 Aircraft is what happens when you build a gun that you want to fly around with. In this case, the gun is the

GAU-8 Avenger 30mm rotary cannon

, and they also managed to find some space to add some bombs and missiles depending on the mission.

British Army Staff Sgt. Robert Leonard, British Army Headquarters 1st Artillery Brigade Joint Terminal Attack Controller, views a feed from an A-10 Thunderbolt II

The GAU.8 is one of the most powerful aircraft cannons ever flown.

Republic of Korea Air Force Joint Terminal Attack Controllers (JTACs) observe as an A-10 Thunderbolt II provides close air support (CAS) during RED FLAG-Alaska 19-2 in the Yukon Training Area.

All pictures by U.S. Air Force, photo by Senior Airman Isaac Johnson.

---