byp4a55 professor6T9

Linux server800.serverconfig.center 6.1.0-48-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.172-1 (2026-05-15) x86_64
Apache
195.242.103.230

File Name : 01-installation.md

---
title: Installation
---

**The Notifications package is pre-installed with the [Panel Builder](/docs/panels).** This guide is for using the Notifications package in a custom TALL Stack application (Tailwind, Alpine, Livewire, Laravel).

## Requirements

Filament requires the following to run:

- PHP 8.1+
- Laravel v10.0+
- Livewire v3.0+

Require the Notifications package using Composer:

```bash
composer require filament/notifications:"^3.2" -W
```

## New Laravel projects

To quickly get started with Filament in a new Laravel project, run the following commands to install [Livewire](https://livewire.laravel.com), [Alpine.js](https://alpinejs.dev), and [Tailwind CSS](https://tailwindcss.com):

> Since these commands will overwrite existing files in your application, only run this in a new Laravel project!

```bash
php artisan filament:install --scaffold --notifications

npm install

npm run dev
```

## Existing Laravel projects

Run the following command to install the Notifications package assets:

```bash
php artisan filament:install --notifications
```

### Installing Tailwind CSS

Run the following command to install Tailwind CSS with the Tailwind Forms and Typography plugins:

```bash
npm install tailwindcss @tailwindcss/forms @tailwindcss/typography postcss postcss-nesting autoprefixer --save-dev
```

Create a new `tailwind.config.js` file and add the Filament `preset` *(includes the Filament color scheme and the required Tailwind plugins)*:

```js
import preset from './vendor/filament/support/tailwind.config.preset'

export default {
    presets: [preset],
    content: [
        './app/Filament/**/*.php',
        './resources/views/filament/**/*.blade.php',
        './vendor/filament/**/*.blade.php',
    ],
}
```

### Configuring styles

Add Tailwind's CSS layers to your `resources/css/app.css`:

```css
@tailwind base;
@tailwind components;
@tailwind utilities;
@tailwind variants;
```

Create a `postcss.config.js` file in the root of your project and register Tailwind CSS, PostCSS Nesting and Autoprefixer as plugins:

```js
export default {
    plugins: {
        'tailwindcss/nesting': 'postcss-nesting',
        tailwindcss: {},
        autoprefixer: {},
    },
}
```

### Automatically refreshing the browser
You may also want to update your `vite.config.js` file to refresh the page automatically when Livewire components are updated:

```js
import { defineConfig } from 'vite'
import laravel, { refreshPaths } from 'laravel-vite-plugin'

export default defineConfig({
    plugins: [
        laravel({
            input: ['resources/css/app.css', 'resources/js/app.js'],
            refresh: [
                ...refreshPaths,
                'app/Livewire/**',
            ],
        }),
    ],
})
```

### Compiling assets

Compile your new CSS and Javascript assets using `npm run dev`.

### Configuring your layout

Create a new `resources/views/components/layouts/app.blade.php` layout file for Livewire components:

```blade
<!DOCTYPE html>
<html lang="{{ str_replace('_', '-', app()->getLocale()) }}">
    <head>
        <meta charset="utf-8">

<title>{{ config('app.name') }}</title>

@filamentStyles
        @vite('resources/css/app.css')
    </head>

<body class="antialiased">
        {{ $slot }}

@livewire('notifications')

@filamentScripts
        @vite('resources/js/app.js')
    </body>
</html>
```

## Publishing configuration

You can publish the package configuration using the following command (optional):

```bash
php artisan vendor:publish --tag=filament-config
```

## Upgrading

> Upgrading from Filament v2? Please review the [upgrade guide](upgrade-guide).

Filament automatically upgrades to the latest non-breaking version when you run `composer update`. After any updates, all Laravel caches need to be cleared, and frontend assets need to be republished. You can do this all at once using the `filament:upgrade` command, which should have been added to your `composer.json` file when you ran `filament:install` the first time:

```json
"post-autoload-dump": [
    // ...
    "@php artisan filament:upgrade"
],
```

Please note that `filament:upgrade` does not actually handle the update process, as Composer does that already. If you're upgrading manually without a `post-autoload-dump` hook, you can run the command yourself:

```bash
composer update

php artisan filament:upgrade
```

Name	Type	Size	Owner/Group	Permission	Last Modified	Actions
.	dir	-	fits-hosting.de_5pri7emmx1j/psacln	0755	2024-10-23 07:36:14
..	dir	-	fits-hosting.de_5pri7emmx1j/psacln	0755	2024-10-23 07:36:14
01-installation.md	text/html	4.62 KB	fits-hosting.de_5pri7emmx1j/psacln	0644	2024-10-23 07:36:14
02-sending-notifications.md	text/plain	12.56 KB	fits-hosting.de_5pri7emmx1j/psacln	0644	2024-10-23 07:36:14
03-database-notifications.md	text/plain	6.46 KB	fits-hosting.de_5pri7emmx1j/psacln	0644	2024-10-23 07:36:14
04-broadcast-notifications.md	text/plain	1.75 KB	fits-hosting.de_5pri7emmx1j/psacln	0644	2024-10-23 07:36:14
05-customizing-notifications.md	text/plain	4.05 KB	fits-hosting.de_5pri7emmx1j/psacln	0644	2024-10-23 07:36:14
06-testing.md	text/plain	2.09 KB	fits-hosting.de_5pri7emmx1j/psacln	0644	2024-10-23 07:36:14
07-upgrade-guide.md	text/plain	3.66 KB	fits-hosting.de_5pri7emmx1j/psacln	0644	2024-10-23 07:36:14

Team Anon Force

https://t.me/Professor6T9x