DEV Community: Fady Mondy

Ship a Laravel Admin Panel in a Day with Filament 5 and TomatoPHP

Fady Mondy — Mon, 12 Oct 2026 11:19:25 +0000

Every Laravel admin panel I've built starts with the same list: users and roles, app settings, English and Arabic, a media library, menus, some content pages, and sooner or later invoices. None of it is your product, but all of it has to work before anyone sees your product. I maintain TomatoPHP, 68 MIT-licensed Filament plugins, and this is the exact order I install them in on Filament 5 when I want that part done in a day. (This post first appeared on tomatophp.com.)

Filament gives you the panel. TomatoPHP gives you those modules as plain composer packages. There are 68 TomatoPHP Filament plugins, all MIT-licensed and released for Filament 5, Laravel 12–13 and PHP 8.2+. Each one registers itself with your panel in one line.

What you end up with

You need	Plugin	Package
Users and roles	User Manager	`tomatophp/filament-users`
App settings (site name, logo, colours, social links)	Settings Hub	`tomatophp/filament-settings-hub`
English + Arabic UI, translated from the panel	Translation Manager + Language Switcher	`tomatophp/filament-translations`, `tomatophp/filament-language-switcher`
Files and images	Media Manager	`tomatophp/filament-media-manager`
Navigation menus	Menu Builder	`tomatophp/filament-menus`
Posts, categories and pages	CMS Builder	`tomatophp/filament-cms`
Invoices and payments	Invoice Manager	`tomatophp/filament-invoices`
Installable app on phones	PWA	`tomatophp/filament-pwa`

Try before you install: demo.tomatophp.com runs 31 TomatoPHP plugins together on Filament 5, with a prefilled demo account. The data resets every hour, so click anything.

Before you start

Start from a fresh Laravel app with a Filament 5 panel:

composer require filament/filament:"^5.0"
php artisan filament:install --panels

Every plugin below follows the same three steps: composer require, run its install command, then add ->plugin(...) to app/Providers/Filament/AdminPanelProvider.php. Some also publish a migration. Each plugin page links to its README with the exact steps, so keep it open while you go.

Morning: the foundation

Users. One package gives you the user resource. If you need roles, the README shows how to pair it with Filament Shield.

composer require tomatophp/filament-users

Settings. Settings Hub stores site settings in the database and gives you a settings page in the panel. Several other TomatoPHP plugins (PWA, invoices) add their own pages to it, so install it early.

composer require tomatophp/filament-settings-hub
php artisan filament-settings-hub:install

Two languages. The Translation Manager scans your code for trans() and __(), stores the strings in the database with a cache, and lets you translate them from the panel. The Language Switcher adds the toggle. English and Arabic work out of the box, including RTL.

composer require tomatophp/filament-translations tomatophp/filament-language-switcher
php artisan filament-translations:install
php artisan filament-language-switcher:install
php artisan filament-translations:import

Midday: content

Media. Media Manager puts a GUI on top of Spatie Media Library: folders, uploads, and a picker you can use in your own forms.

composer require tomatophp/filament-media-manager
php artisan vendor:publish --provider="Spatie\MediaLibrary\MediaLibraryServiceProvider" --tag="medialibrary-migrations"
php artisan filament-media-manager:install

Menus and pages. The Menu Builder stores navigation in the database, so you can render it in the panel or in a Livewire component. The CMS Builder adds posts and categories. Both are translatable, so register lara-zeus/spatie-translatable next to them.

composer require tomatophp/filament-menus tomatophp/filament-cms
php artisan filament-menus:install
php artisan filament-cms:install

One warning from the README: the CMS creates categories and posts tables. If your app already has those, rename yours first.

Afternoon: money

Invoices. The Invoice Manager handles invoices and payments with multiple currencies and invoice types. Call ->useSettingsHub() and its settings appear next to everything else.

composer require tomatophp/filament-invoices
php artisan filament-invoices:install

Before the first invoice, tell it which models invoices are from and for (for example your company and your customers). The README shows the facade call to put in a service provider.

Register everything

With those installed, the panel provider looks roughly like this (check each README for the options you want):

use Filament\Panel;

public function panel(Panel $panel): Panel
{
    return $panel
        // ...
        ->plugin(\TomatoPHP\FilamentUsers\FilamentUsersPlugin::make())
        ->plugin(\TomatoPHP\FilamentSettingsHub\FilamentSettingsHubPlugin::make()
            ->allowSiteSettings()
            ->allowSocialMenuSettings())
        ->plugin(\TomatoPHP\FilamentTranslations\FilamentTranslationsPlugin::make())
        ->plugin(\TomatoPHP\FilamentLanguageSwitcher\FilamentLanguageSwitcherPlugin::make())
        ->plugin(\TomatoPHP\FilamentMediaManager\FilamentMediaManagerPlugin::make())
        ->plugin(\LaraZeus\SpatieTranslatable\SpatieTranslatablePlugin::make()
            ->defaultLocales(['en', 'ar']))
        ->plugin(\TomatoPHP\FilamentMenus\FilamentMenusPlugin::make())
        ->plugin(\TomatoPHP\FilamentCms\FilamentCMSPlugin::make()
            ->useCategory()
            ->usePost())
        ->plugin(\TomatoPHP\FilamentInvoices\FilamentInvoicesPlugin::make()
            ->useSettingsHub());
}

Run php artisan migrate, sign in, and you have a bilingual admin panel with users, settings, media, menus, content and invoices. That is the part every client expects and nobody pays extra for.

What this won't do for you

It won't design your domain. The plugins cover the generic modules. Your orders, bookings or patients are still your code, and that's where the day you saved should go.
Read the README of each plugin. Some publish migrations or need a companion package. The compatibility table at the top tells you which major version matches your Filament.
Not every repo is a finished plugin. The TomatoPHP organisation has more repos than the 68 released Filament plugins. Use what's listed on the plugins page, which is the maintained set.

How the plugins are maintained

During the Filament 5 upgrade, every plugin went through the same release gate before it was tagged: open issues fixed and community PRs merged with credit, a green Pest suite with a regression test for each fix, and then a real install in a sandbox Laravel 13 + Filament 5 app where a smoke test renders every panel page with zero skipped. The same pass found and fixed real security bugs, for example unescaped user HTML in the docs, blog and notes plugins, and payment gateway secrets that were reaching the browser.

The packages have more than 1.7 million installs on Packagist, and the source is on GitHub.

Next steps: browse all plugins · read the docs · try the live demo

Originally published on tomatophp.com.

How to Ship an Official MCP Server for Your SaaS in 2 Weeks

Fady Mondy — Sun, 11 Oct 2026 12:39:50 +0000

Originally published at fadymondy.com.

Your customers are starting to ask a new question in sales calls and support tickets: "Does it work with Claude?" Sometimes it is ChatGPT or Cursor instead, but the request is the same. They want to ask their AI assistant to do real work inside your product, without copying data between tabs.

The standard way to make that happen is an MCP server. The Model Context Protocol is the open protocol AI assistants use to discover and call tools in other products. If you already have a decent API, an official MCP server is a small, well-bounded project. Here is how I plan and ship one in about two weeks, and what to decide before anyone writes code.

What an MCP server actually is (for a SaaS team)

An MCP server is a thin layer that sits beside your product and talks to your existing API. It exposes a short list of tools, each with a name, a plain-language description and a typed input schema. The assistant reads those descriptions, decides which tool fits the user's request, and calls it.

Three things follow from that:

Your backend doesn't change. The server is a client of your API, like your web app is.
Your language doesn't matter. I usually build in TypeScript or Go, or PHP for Laravel products, whatever your team can maintain.
Tool design matters more than code volume. Most of the work is deciding what the assistant should be able to do, and describing it so the model picks the right tool.

There are two common ways to run one: remote (a hosted HTTP endpoint your cloud customers connect to with OAuth) and local (a package the user runs on their machine, which suits self-hosted installs). Many SaaS products start with remote.

Why "official" matters

If you don't ship one, someone else might. Community MCP servers for popular products appear quickly, and they usually ask users to paste a full-access API key into a config file. Your customers then run unvetted code with their production credentials, and you get the support tickets.

An official server lets you control three things: which actions are exposed, how authentication works, and how your product is described to the assistant.

The 2-week plan

Two weeks is realistic when the API exists and is documented, and the first version focuses on the 10–20 actions people actually ask for. Here is the sequence I use.

Step 0: a one-page tool spec (before any commitment)

Before building, I read your API docs and write a one-page spec. It lists the proposed tools, what each one does, its inputs, whether it reads or writes, and which auth scope it needs. It is the cheapest way for both sides to see whether the project makes sense.

A good spec answers:

What are the five things a user will ask the assistant to do on day one?
Which of those are read-only and which change data?
Which actions are destructive or expensive and need a clear warning?
What does the assistant need to find things (search, filters, IDs)?

Days 1–3: tool design and scaffolding

Turn the spec into tool definitions. Keep the list short and the names obvious. Don't mirror every endpoint. An assistant does better with find_customer and create_invoice than with forty CRUD endpoints that differ by one field.

Write the descriptions as instructions to the model: when to use the tool, what it returns, and what not to use it for. In my experience this is the work that most changes how well the server performs.

On my own servers, tools live in a registry: one list the protocol layer reads. Adding a tool later means adding one entry, not touching the transport or auth plumbing. It keeps the server easy to grow after handover.

Days 4–7: authentication and permissions

This is where an official server earns its name.

OAuth for remote servers. The MCP authorization spec is built on OAuth 2.1. On Zekra's remote MCP endpoint I implemented the full flow: PKCE (S256), dynamic client registration and per-brain consent, with access re-checked against current membership on every call.
Scoped API keys as a fallback. In Moharrik, keys are read-only by default and expire after 90 days.
Read and write separated. Mark read-only tools as read-only (MCP tool annotations support readOnlyHint and destructiveHint). On Zekra, adding read-only annotations let AI coding agents and other MCP clients run recall and list tools without an approval prompt, while writes still ask.
Make agent actions traceable. When an assistant writes data, record that it was an agent. On my issue tracker, comments created over MCP are stored with author_kind = 'agent', so a human can always tell them apart.

Days 8–10: test against real assistants

Unit tests aren't enough. Connect the server to Claude, ChatGPT and Cursor and run the prompts from the spec. Watch for:

the assistant picking the wrong tool (fix the description, not the model);
tools returning too much data (paginate and trim; context is not free);
vague errors (return messages the assistant can act on, like "customer not found, try search_customers").

Days 11–14: docs, listing and handover

Setup guides for each assistant: one page each, with the exact config.
A permissions page that explains in plain language what each scope allows. In Moharrik this explainer is generated from the tool registry, so it can't drift from the code.
Listings in the main MCP directories, so users can find the official server.
Handover. The repository, deployment notes and a short walkthrough. The code ships under your name and licence.

What stretches past two weeks

Be honest about scope up front. These usually add time:

no public API yet, or an API that can't do what users ask;
complex multi-tenant permissions that aren't modelled in the API;
long-running jobs that need progress reporting or webhooks;
a self-hosted package and a remote endpoint in the first release.

None of them blocks a project. They belong in the spec so the plan and the price stay fixed.

Checklist before you start

[ ] Your API is documented and stable enough to build against.
[ ] You have listed the top 5 user requests the assistant should handle.
[ ] You know which actions must never run without a confirmation.
[ ] You have decided on remote, local or both.
[ ] Someone on your team will own the server after handover.

Proof, not promises

I build MCP servers for my own products, and they run in production:

Orchestra MCP: an AI-agentic IDE framework with a plugin-host architecture.
Zekra: shared memory for AI agents, served over a remote MCP endpoint with OAuth 2.1.
Moharrik: a CRM with inbox and WhatsApp that is fully operable over MCP.
Nasaq UI: an open-source design system with its own MCP server.

If you want the same for your product, see MCP server development. The process starts with a free one-page tool spec.

Why You Should Pay for Open Source

Fady Mondy — Tue, 08 Oct 2024 13:59:23 +0000

Almost every developer uses open-source projects daily, whether it's writing code in VS Code, speeding up development with TailwindCSS, or building robust web applications with Laravel, the most popular PHP framework. And let’s not forget FilamentPHP for admin panel creation.

These projects aren’t built by ghosts; they’re created by people—some of the best in their fields. They aren’t just doing their jobs; they’re making the work of others easier, faster, and more efficient.

Case Study

Let’s consider a scenario where the Laravel framework didn’t exist. Before Laravel, building a stable, secure, and SOLID-compliant MVC structure with PHP 5.7 was a daunting task. However, Taylor Otwell recognized this challenge and, without asking for payment, worked hard to create Laravel, revolutionizing PHP development.

Imagine if Taylor hadn’t received community support—Laravel, and perhaps even PHP itself, might have faded away. Thankfully, he did get support, grew a team, and even launched open-source tools like "Herd" for free. Today, Laravel receives substantial funding ($57M), allowing it to thrive while remaining open and free to use.

Is Open Source Really Free?

Most open-source projects operate under MIT licenses, meaning they’re free to use, modify, or clone. But “free to use” doesn’t mean “free of cost.” Open-source developers invest their time and expertise to create and maintain these projects. If you’re using open-source software and earning from it, you should sponsor or contribute to these projects, supporting the people behind them.

How Can You Contribute?

Visit GitHub, check out the repositories you use daily, and support their creators. Even $1 can make a difference to a developer, showing them that their work is valued.

If you can’t contribute financially, help by sharing their work. Spread the word through blogs, social media, or even videos. Exposure can drive others to contribute, ensuring the continued growth of open-source projects.

Let’s support the community so we can continue to benefit from more innovative open-source tools!

Join TomatoPHP Community

Fady Mondy — Sun, 06 Oct 2024 13:51:17 +0000

Hello, Developers!

We are thrilled to announce the launch of the TomatoPHP Public Profile! As we continue to grow, our goal is to make the TomatoPHP community more engaging and feature-rich, offering tools and opportunities that help developers thrive.

But we aren’t doing this alone. Our progress is powered by the collective efforts of our incredible team, contributors, and sponsors. To foster even more collaboration and engagement, we’ve introduced a new feature: Public Profiles.

With this feature, you can now join our community and create demos of our packages. But this is just the beginning. As we continue to develop, we plan to roll out even more exciting features, including:

Create and share blog posts within the community.
Submit your open-source projects to be featured under the TomatoPHP umbrella.
Generate a personalized QR code for easy sharing of your public profile.
Post sticky notes and share them with friends via a public URL.
Engage with community activity, including posts, comments, and likes.
Manage your invoices and other essential tools directly from your profile.
Track and manage your GitHub open-source projects and issues seamlessly.

We believe these features will help make our community more connected, collaborative, and productive. We can’t wait to see how you’ll use these new tools to contribute to the TomatoPHP ecosystem!

All of these features is open-source and you can check our repo

Thank you for being part of this journey. Together, we’re building something special. Join Us

TomatoPHP Filament Plugins

Fady Mondy — Wed, 19 Jun 2024 19:05:45 +0000

Hello, Laravel and PHP enthusiasts!

We are excited to announce that we are enhancing our contributions to the Laravel & PHP community. Our team is developing a series of powerful packages and plugins for FilamentPHP, bringing the robust features of the TomatoPHP framework directly to your Filament applications. Stay tuned for more updates and take your Filament apps to the next level with TomatoPHP!

Use Plugin as a Module

before use this feature please make sure that you are publish the config file of modules.php using this command

 php artisan vendor:publish --provider="Nwidart\Modules\LaravelModulesServiceProvider" --tag="config"

on the config file edit this 'enabled' => true,

<?php

return [
    /*
    |--------------------------------------------------------------------------
    | Scan Path
    |--------------------------------------------------------------------------
    |
    | Here you define which folder will be scanned. By default will scan vendor
    | directory. This is useful if you host the package in packagist website.
    |
    */
    'scan' => [
        'enabled' => true,
        'paths' => [
            base_path('vendor/*/*'),
        ],
    ],
]

all of this plugin can work as a module inside your app using our filament-plugins package and use this command

php artisan filament-plugins:publish

and type the name of the plugin you went to publish, if you don't know the plugin name you can use the list of all plugins using this command

php artisan module:list

Plugins List

here is the plugins list you can use.

Filament Users

User Table Resource with a lot of package integrations

Filament Users V2
Filament Users V1

Filament Translations

Manage your translation with DB and cache, you can scan your language tags like trans(), __(), and get the string inside and translate them using UI.

Filament Translations V2
Filament Translations V1

Filament Plugins

Manage your modules as a plugin system with a plugin generator

Filament Plugins

Filament Media Manager

Manage your media files using spatie media library with easy to use GUI for FilamentPHP

Filament Media Manager

Filament Developer Gate

Secure your selected route by using a middleware with a static password for developers only

Filament Developer Gate

Filament Accounts

full accounts manager with API/Notifications/Contacts to manage your contacts and accounts

Filament Accounts

Filament Wallet

Account Balance / Wallets Manager For FilamentPHP and Filament Account Builder

Filament Wallet

Filament Alerts

Send notifications to users using notification templates and multi-notification channels

Filament Alerts

Filament FCM

Firebase Cloud Messaging integration to Native FilamentPHP Notification Package

Filament FCM

Filament Helpers

Helper Class Generator to manage your forms and table inside your filament app

Filament Helpers

Filament Icons

Picker & Table Column & Icons Provider for FilamentPHP

Filament Icons

Filament CMS

Full CMS System with easy-to-use page builder & theme manager for FilamentPHP

Filament CMS

Filament Types

Manage any type on your app in the Database with easy Resources for FilamentPHP

Filament Types

Filament Menus

Menu Database builder to use as a navigation on Filament Panel or as a Livewire Component

Filament Menus

Filament Browser

File & Folders & Media Browser With Code Editor

Filament Browser

Filament Artisan

Simple yet powerful library for running some artisan commands. this package is a fork of artisan-gui with some custom for filament UI

Filament Artisan

Filament Settings Hub

Manage your app settings with GUI and helpers

Filament Settings Hub

Filament Locations

Database Seeds for Locations for FilamentPHP

Filament Locations

Filament Splade

Integration of Splade Vue Components for Filament

Filament Splade

Filament API

Generate APIs from your filament resource using a single line of code

Filament API

Filament E-commerce

Build your own e-commerce store with FilamentPHP with the Power of Tomato CMS Builder

Filament E-commerce

Filament Twilio

Send Whatsapp messages using Twilio and native filament Notification Facade class

Filament Twilio

Filament Discord

Send Notification to discord channel Webhook using native FilamentPHP Notification Facade class

Filament Discord

Filament Translation Component

Translation Component as a key/value to use it with Spatie Translatable FilamentPHP Plugin

Filament Translation Component

Filament Sticky Notes

Add Sticky Notes to your FilamentPHP dashboard with tons of options and style

Filament Sticky Notes

Filament Invoices Manager

Generate and manage your invoices / payments using multi currencies and multi types in FilamentPHP

Filament Invoices Manager

Filament PWA

get a PWA feature on your FilamentPHP app with settings from panel

Filament PWA

Filament Simple Theme

A simple theme for FilamentPHP with custom user menu in sidebar

Filament Simple Theme

Filament Subscriptions

Manage subscriptions and feature access with customizable plans in FilamentPHP

thanks for Laravel Subscriptions you can review it before use this package.

Filament Subscriptions

Filament POS

POS System for FilamentPHP with a lot of features and integration with Ecommerce Builder

Filament POS

Filament Tenancy

Tenancy multi-database integration for FilamentPHP

Filament Tenancy

Filament Withdrawals

Manage your withdrawals in Filament

Filament Withdrawals

Filament Payment Manager

Manage your payments inside FilamentPHP app with multi payment gateway integration

Filament Payment Manager

Filament User Logger

Log all user activity to file or log driver and preview it on your FilamentPHP panel

Filament User Logger

Filament SEO Manager

Manage and generate SEO tags and integrate your website with Google SEO services

Filament SEO Manager

Filament Documents Editor

Manage your documents and contracts all in one place with template builder

Filament Documents Editor

Filament Social Media Manager

Integration of social media platform actions and auth to your FilamentPHP panel

Filament Social Media Manager

Filament Blog Template

Frontend for CMS Builder to build a blog and personal websites

Filament Blog Template

Support

you can join our discord server to get support TomatoPHP

Docs

you can check docs of all packages on Docs

Credits

Changelog

Please see CHANGELOG for more information on what has changed recently.

License

The MIT License (MIT). Please see License File for more information.

CircleXO Open Source Social Network Build In TomatoPHP

Fady Mondy — Thu, 28 Mar 2024 06:50:54 +0000

It's Circles

Open Source Social Network built for Businesses, with tons of apps

What is CircleXO?

CircleXO is an open source social media platform build for Businesses

Why i must use CircleXO?

if you like to share your works, games, media to the world with a full custom open source platform, so it's a must

How CircleXO Work?

Our platform built in TomatoPHP a full-stack Laravel framework, built for make development more fast and easy

Features

Feature Highlights

Listing

Generate listings of your interests, skills and links easily.

QR Generator

Have a QR code that you can use to send someone your profile or connect with them instantly, enabling quick networking.

Social Network

Be part of a vibrant community where you can interact and discuss matters, share updates.

Open Source

It's built on open-source platform, ensuring transparency and continuous improvement through community involvement.

Messages

Use private messaging to communicate people.

Sponsoring

Get your projects, events or initiatives sponsored.

Install on your local

git clone git@github.com:tomatophp/circlexo.git
cd circlexo
cp .env.example .env

create new database circlexo and update .env file

DB_DATABASE=circlexo
DB_USERNAME=root
DB_PASSWORD=12345678

composer install
php artisan key:generate
php artisan config:cache
php artisan migrate

build assets

yarn
yarn build

Create New Account

you can create a new account by using this link

Join Open Source

you can join us on GitHub on this link

TomatoPHP SaaS Demo

Fady Mondy — Wed, 14 Feb 2024 11:55:11 +0000

It's finally here – welcome to the TomatoPHP SaaS Demo!

Now, you have the opportunity to create your very own SaaS application for free. Explore all the incredible features and packages TomatoPHP has to offer. And if you encounter any errors while exploring our package repository, please don't hesitate to report them.

Start building your demo now at https://tomatophp.com/.

Thank you for your continued support – let's embark on this exciting journey together!

Build E-Commerce System in Seconds With TomatoPHP

Fady Mondy — Wed, 31 Jan 2024 12:26:42 +0000

hi, community.

Introducing #tomatophp, a cutting-edge open-source Laravel package designed to streamline development within the VILT stack environment. This innovative ecosystem leverages the power of Splade to effortlessly generate modern, high-performance single-page applications (SPAs) using only Blade files. #tomatophp redefines the development experience, making it both efficient and enjoyable.

As we progress, we continuously enhance our ecosystem by incorporating additional features into our plugins. Presently, we have developed a comprehensive e-commerce system using these plugins. In this article, we will guide you through the implementation process, demonstrating how you can seamlessly integrate a robust e-commerce system into your application.

Install Tomato Admin

you need to install tomato-admin plugin on your fresh Laravel app so let's create a new Laravel app.

composer create-project laravel/laravel tomato

if you don't have an environment for Laravel you can use this doc to build one on your Ubuntu Linux.

now cd inside your project folder change .env of your database and make sure that your Laravel app is running and the database is connected, you can check that by running migrations

php artisan migrate

now let's start installing tomato-admin

composer require tomatophp/tomato-admin

after the composer is done run this command for auto-install

php artisan tomato-admin:install

if you are using macOS you can easily use auto yarn package install if not just build your assets like this

yarn & yarn build

now you have tomato-admin installed on your Laravel project.

we will use some media on our package to we need to publish Spatie Media Library migrations

php artisan vendor:publish --provider="Spatie\MediaLibrary\MediaLibraryServiceProvider" --tag="medialibrary-migrations"

if this command does not work please use this command

php artisan vendor:publish

then on the search type media and select the migration one.

now migrate your files

php artisan migrate

you can check your browser now and you will see a homepage like this

we need to change HOME const on the RouteServiceProvider.php to be /admin to make the redirect after auth to admin.

Install Tomato Roles

No e-commerce system is complete without a robust role management structure. To fulfill this essential requirement, we'll be installing 'tomato-roles' to seamlessly handle roles within our mission to build a comprehensive e-commerce system.

composer require tomatophp/tomato-roles

after the composer is done run this command

php artisan tomato-roles:install

now go to your app\Models\User.php and add this trait to it

use \Spatie\Permission\Traits\HasRoles;

now your dashboard is ready to log in using admin@admin.com and password as a password from this URL /admin/login

if you try to access any page you will be redirected to Two-factor Confirmation If you don't go it for now, you can easily stop it by removing implements MustVerifyEmail from your User.php model.

Install Tomato CRM

As an integral part of our e-commerce system, the management of customer interactions, authentications, and other crucial actions is paramount. To efficiently handle these aspects, we'll be installing 'tomato-crm.' Let's proceed with the installation to empower our system with advanced customer relationship management capabilities.

composer require tomatophp/tomato-crm

now let's install it

php artisan tomato-crm:install

let's publish Accounts.php model to our app to custom it

php artisan vendor:publish --tag="tomato-crm-model"

and you need to publish tomato-crm config

php artisan vendor:publish --tag="tomato-crm-config"

on tomato-crm.php config change the model path to like this

"model" => \App\Models\Account::class,

now we need to add a new guard to our app, so let's add it on the config auth.php like this.

<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Authentication Defaults
    |--------------------------------------------------------------------------
    |
    | This option controls the default authentication "guard" and password
    | reset options for your application. You may change these defaults
    | as required, but they're a perfect start for most applications.
    |
    */

    'defaults' => [
        'guard' => 'web',
        'passwords' => 'users',
    ],

    /*
    |--------------------------------------------------------------------------
    | Authentication Guards
    |--------------------------------------------------------------------------
    |
    | Next, you may define every authentication guard for your application.
    | Of course, a great default configuration has been defined for you
    | here which uses session storage and the Eloquent user provider.
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | Supported: "session"
    |
    */

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
        'accounts' => [
            'driver' => 'session',
            'provider' => 'accounts',
        ]
    ],

    /*
    |--------------------------------------------------------------------------
    | User Providers
    |--------------------------------------------------------------------------
    |
    | All authentication drivers have a user provider. This defines how the
    | users are actually retrieved out of your database or other storage
    | mechanisms used by this application to persist your user's data.
    |
    | If you have multiple user tables or models you may configure multiple
    | sources which represent each model / table. These sources may then
    | be assigned to any extra authentication guards you have defined.
    |
    | Supported: "database", "eloquent"
    |
    */

    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\Models\User::class,
        ],
        'accounts' => [
            'driver' => 'eloquent',
            'model' => App\Models\Account::class,
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | Resetting Passwords
    |--------------------------------------------------------------------------
    |
    | You may specify multiple password reset configurations if you have more
    | than one user table or model in the application and you want to have
    | separate password reset settings based on the specific user types.
    |
    | The expiry time is the number of minutes that each reset token will be
    | considered valid. This security feature keeps tokens short-lived so
    | they have less time to be guessed. You may change this as needed.
    |
    | The throttle setting is the number of seconds a user must wait before
    | generating more password reset tokens. This prevents the user from
    | quickly generating a very large amount of password reset tokens.
    |
    */

    'passwords' => [
        'users' => [
            'provider' => 'users',
            'table' => 'password_reset_tokens',
            'expire' => 60,
            'throttle' => 60,
        ],
    ],

    /*
    |--------------------------------------------------------------------------
    | Password Confirmation Timeout
    |--------------------------------------------------------------------------
    |
    | Here you may define the amount of seconds before a password confirmation
    | times out and the user is prompted to re-enter their password via the
    | confirmation screen. By default, the timeout lasts for three hours.
    |
    */

    'password_timeout' => 10800,

];

now clear your config cache

php artisan config:clear

now rebuild your assets

yarn & yarn build

now your CRM is ready you can check it on your dashboard

Install Tomato Wallet

For seamless transaction management between customers and vendors within the e-commerce system, a robust payment handler is crucial. Introducing 'tomato-wallet,' a feature-rich package that not only manages customer wallets but also seamlessly handles payments. Packed with a multitude of integrated payment gateways, 'tomato-wallet' ensures a magical experience in managing transactions. Let's proceed with the installation to unlock the full potential of this powerful payment solution.

composer require tomatophp/tomato-wallet

let's install it

php artisan tomato-wallet:install

now we need to implement Wallet interface to our Account.php and add HasWallet trait to it to make the wallet of the customer work, your Account model must be like this

<?php

namespace App\Models;

use Bavix\Wallet\Interfaces\Wallet;
use Bavix\Wallet\Traits\HasWallet;
use Illuminate\Database\Eloquent\Factories\HasFactory;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Foundation\Auth\User as Authenticatable;
use Illuminate\Notifications\Notifiable;
use Laravel\Sanctum\HasApiTokens;
use Spatie\Macroable\Macroable;
use Spatie\MediaLibrary\HasMedia;
use Spatie\MediaLibrary\InteractsWithMedia;
use Spatie\Permission\Traits\HasRoles;
use TomatoPHP\TomatoCrm\Models\Group;

/**
 * @property integer $id
 * @property string $name
 * @property string $username
 * @property string $loginBy
 * @property string $address
 * @property string $type
 * @property string $password
 * @property string $otp_code
 * @property string $otp_activated_at
 * @property string $last_login
 * @property string $agent
 * @property string $host
 * @property integer $attempts
 * @property boolean $login
 * @property boolean $activated
 * @property boolean $blocked
 * @property string $deleted_at
 * @property string $created_at
 * @property string $updated_at
 * @property AccountsMeta[] $accountsMetas
 * @property Activity[] $activities
 * @property Comment[] $comments
 * @property Model meta($key, $value)
 * @property Location[] $locations
 */
class Account extends Authenticatable implements HasMedia, Wallet
{
    use InteractsWithMedia;
    use HasApiTokens, HasFactory, Notifiable;
    use HasWallet;

    /**
     * @var array
     */
    protected $fillable = [
        'email',
        'phone',
        'parent_id',
        'type',
        'name',
        'username',
        'loginBy',
        'address',
        'password',
        'otp_code',
        'otp_activated_at',
        'last_login',
        'agent',
        'host',
        'is_login',
        'is_active',
        'deleted_at',
        'created_at',
        'updated_at'
    ];

    protected $casts = [
        'is_login' => 'boolean',
        'is_active' => 'boolean'
    ];
    protected $dates = [
        'deleted_at',
        'created_at',
        'updated_at',
        'otp_activated_at',
        'last_login',
    ];


    protected $appends = [
        'birthday',
        'gender',
        'more'
    ];

    public function getMoreAttribute()
    {
        $metas = $this->accountsMetas()->get()->pluck('value', 'key')->toArray();
        return $metas;
    }

    public function getBirthdayAttribute()
    {
        return $this->meta('birthday') ?: null;
    }

    public function getGenderAttribute()
    {
        return $this->meta('gender') ?: null;
    }

    /**
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
     */
    public function accountsMetas()
    {
        return $this->hasMany('TomatoPHP\TomatoCrm\Models\AccountsMeta');
    }

    /**
     * @param string $key
     * @param string|null $value
     * @return Model|string
     */
    public function meta(string $key, string|null $value=null): Model|string|null
    {
        if($value){
            return $this->accountsMetas()->updateOrCreate(['key' => $key], ['value' => $value]);
        }
        else {
            return $this->accountsMetas()->where('key', $key)->first()?->value;
        }
    }
    /**
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
     */
    public function activities()
    {
        return $this->hasMany('TomatoPHP\TomatoCrm\Models\Activity');
    }

    /**
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
     */
    public function comments()
    {
        return $this->hasMany('TomatoPHP\TomatoCrm\Models\Comment');
    }

    /**
     * @return \Illuminate\Database\Eloquent\Relations\HasMany
     */
    public function locations()
    {
        return $this->hasMany('TomatoPHP\TomatoCrm\Models\Location');
    }

    public function groups(){
        return $this->belongsToMany(Group::class, 'account_groups', 'account_id', 'group_id');
    }
}

now your wallet is working you can start any transaction and check the customer's balance.

Install Tomato CMS

In any functioning e-commerce setup, a well-optimized front end is indispensable. To enhance SEO performance and add essential content such as posts and pages, we'll be incorporating our 'tomato-cms' package. Let's proceed with the installation to seamlessly integrate this package and elevate our e-commerce platform.

composer require tomatophp/tomato-cms

now let's install it

php artisan tomato-cms:install

Install Tomato Themes

To craft a dynamic frontend tailored as a theme, we'll be utilizing the 'tomato-themes' package. This package simplifies the implementation of multi-themes for your project, employing a Hierarchical Model-View-Controller (HMVC) architecture. Let's initiate the installation process for 'tomato-themes' to facilitate the seamless integration of diverse themes into your project.

composer require tomatophp/tomato-themes

now let's install it

php artisan tomato-themes:install

now rebuild your assets

yarn & yarn build

make sure that you have Themes folder in your project root and add this line to your composer.json

    "autoload": {
        "psr-4": {
            "App\\": "app/",
            "Database\\Factories\\": "database/factories/",
            "Database\\Seeders\\": "database/seeders/",
            "Themes\\": "Themes/"
        }
    },

now you need to reload the composer

composer dump-autoload

now inside your tailwind.config.js add these lines

content: [
    ...
    "./Themes/**/*.blade.php",
    "./Themes/**/**/*.blade.php",
],

now your theme is ready to upload or create a new theme.

Install Tomato E-Commerce

Now that we have our foundational elements in place, including a ready CRM, role management, and several essential packages, it's time to bring it all together by installing the E-Commerce System. The seamless integration of these components promises a robust and feature-rich platform. Let's proceed with the installation to witness the culmination of our efforts in building a comprehensive and efficient E-Commerce System.

composer require tomatophp/tomato-ecommerce

let's install it

php artisan tomato-ecommerce:install

now everything i ready to install our e-commerce theme.

this package will install tomato-products, tomato-orders, tomato-offers, tomato-branches for you

to make everything work fine you need some actions, we need to install tomato-branches

php artisan tomato-branches:install

after that, you need to create just 1 Shipping Vendor from this endpoint /admin/shipping-vendors

now you need to change your site SEO data and your site Logo from this endpoint /admin/settings/seo upload your logos and change the Site Name.

Install E-commerce Theme

Having established a solid foundation, including CRM, role management, and various essential packages, we're now ready to enhance the visual appeal of our E-Commerce and CMS platforms. Introducing our user-friendly theme with a simple yet stylish design – an ideal canvas for customization. Let's embark on the installation process to seamlessly integrate this theme and provide users the flexibility to tailor it to their preferences.

inside your Themes Folder clone this repo

cd Themes

now clone our Theme.

git clone git@github.com:tomatophp/Ecommerce.git

now go to your dashboard /themes and you will get the new theme you can just activate it.

Please note that you must not have / route on your main routes/web.php because these routes can override the Theme Routes.

to fix style rebuild your assets

yarn & yarn build

now if you check your home page you will get something like this

you can select from the top dropdown any section and add it to your page.

and you can build a menu from /admin/menus using this endpoint

Home /
About /about
Shop /shop
Blog /blog
Contact /contact
Terms & Conditions /terms
Privacy /privacy

you can create 2 menus main, footer the main will show up auto to your header and the footer to your footer.

change the middleware of Authenticate redirect to this route

<?php

namespace App\Http\Middleware;

use Illuminate\Auth\Middleware\Authenticate as Middleware;
use Illuminate\Http\Request;

class Authenticate extends Middleware
{
    /**
     * Get the path the user should be redirected to when they are not authenticated.
     */
    protected function redirectTo(Request $request): ?string
    {
        return $request->expectsJson() ? null : route('accounts.login');
    }
}

now in your Account.php model add this trait

    use \TomatoPHP\TomatoEcommerce\Services\Traits\InteractsWithEcommerce;
    use \TomatoPHP\TomatoNotifications\Traits\InteractWithNotifications;
    use \TomatoPHP\TomatoOrders\Services\Traits\InteractsWithOrders;

With the successful installation of our comprehensive E-commerce system, you are now equipped to seamlessly manage your product catalog. Begin by adding new products and defining categories to tailor your offerings. Feel empowered to kickstart the order creation process, as your E-commerce system stands ready to facilitate smooth transactions and streamline your online business operations.

🍅 Thanks for using Tomato Plugins & TomatoPHP framework
💼 Join the support server on Discord here
📄 You can check docs here
⭐ Please give us a star on any repo if you like it TomatoPHP GitHub
🤝 Sponsor us here

Install Ubuntu Desktop on Any Ubuntu Server

Fady Mondy — Mon, 16 Oct 2023 13:53:36 +0000

some developers need to use a cloud server as a personal computer for fast development and remote use, and it's a very good idea but, how can install an Ubuntu desktop on it?

it's easy to do this by following some commands:

let's start by installing tasksel

 sudo apt install -y tasksel

now you are ready to install ubuntu-desktop use this command

sudo apt install -y ubuntu-desktop

cloud servers by default don't have a display so you need to set a graphical target to up the GUI

sudo systemctl set-default graphical.target

and WOW, it's working now.

Install XRDP

if you like to get a Remote control using RDP you can follow these steps, let's start by installing xrdp

sudo apt install xrdp -y

now we need to add SSL to xrdp using this command

usermod -a -G ssl-cert xrdp

now we need to add some commands to make xrdp auto-start

echo 'Unset DBUS_SESSION_ADDRESS' >> /etc/xrdp/startwm.sh
echo 'Unset XDG_RUNTIME_DIR' >> /etc/xrdp/startwm.sh

now xrdp is ready to connect we have just 1 step, we need to allow port 3389 to access xrdp

ufw allow from 192.168.1.0/24 to any port 3389
ufw reload

now you can connect with any RDP client to your remote server.

Install Laravel Valet+ Ubuntu

Fady Mondy — Mon, 16 Oct 2023 13:41:49 +0000

we are recommending using our environment to make the project work we are using Ubuntu Linux and Laravel valet+

Install BackBox Linux "Recommendation"

I like to use BackBox Linux because it has a lot of tools and supports our environment, so from the link, we keep downloading the ISO image and putting it in USB using Rufus and then booting your computer into it

Install dependencies packages

let's start by opening our terminal and updating the system to the last one, and after that install some packages

sudo add-apt-repository -y ppa:nginx/stable
sudo apt install software-properties-common
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update

sudo apt-get upgrade

after it finished reboot your computer and after that run this command

sudo apt-get install network-manager libnss3-tools jq xsel

Install PHP & its extensions

sudo apt install php8.2-fpm

sudo apt install php8.2-cli php8.2-common php8.2-curl php8.2-mbstring php8.2-opcache php8.2-readline php8.2-xml php8.2-zip php8.2-mysql php8.2-gd

Install MySql Server

sudo apt-get -y install mysql-server

sudo mysql_secure_installation

use 0 for the password and use any password something like 12345678

after the installation is finished, start the MySQL server

sudo mysql

and on the MySQL server console use this command

mysql> ALTER USER 'root'@'localhost' IDENTIFIED WITH mysql_native_password BY '12345678';

mysql> FLUSH PRIVILEGES;

mysql> exit;

Install Composer

sudo apt install curl

curl -sS https://getcomposer.org/installer | sudo php -- --install-dir=/usr/local/bin --filename=composer

Install PHPMyAdmin

the valet has been installed now, let's go and install PHPMyAdmin and link it with the .test subdomain using valet first of all, create a folder for your sites on the home directory ~

cd ~
mkdir Sites
cd Sites

now we are on the Sites path, let's park this directory to be the directory of our projects

valet park

now any project on this directory will be auto-linked with subdomain .test, let's download PHPMyAdmin from this link and unzip the file inside the Sites directory and rename the folder to PHPMyAdmin, after that go inside the folder and use this command

cp config.sample.inc.php config.sample.php
nano config.sample.php

change the line to

$cfg['blowfish_secret'] = 'YK07LhNSe50vrj,HwBfb.l3gpbv;u8b7',

now use CTRL + x and say Y now we will use valet to link PHPMyAdmin and secure the link with SSL

valet link
valet secure
valet open

now you can see the PHPMyAdmin working and you can use root as the user and the password you created to MySQL to login

Install Valet

composer global require genesisweb/valet-linux-plus

no, you need to export Valet use

PATH="$PATH:$HOME/.composer/vendor/bin"

Or use the following

PATH="$PATH:$HOME/.config/composer/vendor/bin"

and now it will be easy to start installing valet

valet install

it will ask you for a password input 12345678

Pro Terminal for Pro Developer OhMyZsh

Fady Mondy — Mon, 16 Oct 2023 13:34:08 +0000

as we like to make everything more easy for our community, in this article we will explain how you can get your terminal to be like this one.

Install OhMyZsh

we start by installing zsh and ohMyZsh packages to add their features to our terminal

sudo apt-get -y install git curl wget
sudo apt-get -y install zsh
sh -c "$(curl -fsSL https://raw.githubusercontent.com/ohmyzsh/ohmyzsh/master/tools/install.sh)"

now zsh and OhMyZsh are installed successfully, we will add some plugins to make it easier to use the terminal.

Install OhMyZsh Plugins

we will add 2 plugins syntax-highlighting and zsh-autosuggestions These 2 plugins make the code and command on the terminal highlighted and the code you right will be saved to your terminal it will auto-complete it for you

git clone https://github.com/zsh-users/zsh-syntax-highlighting.git ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlighting
echo "source ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-syntax-highlightingzsh-syntax-highlighting.zsh" >> ${ZDOTDIR:-$HOME}/.zshrc
git clone https://github.com/zsh-users/zsh-autosuggestions ${ZSH_CUSTOM:-~/.oh-my-zsh/custom}/plugins/zsh-autosuggestions

now you need to allow this plugin on the OhMyZsh config

sudo nano ~/.zshrc

search about plugins and add this

plugins=( 
    git
    zsh-syntax-highlighting
    zsh-autosuggestions
)

Install Power Fonts

to make OhMyZsh work with icons you need to install this font

sudo apt-get install fonts-powerline

and you can download it from here

Install PowerLevel10k Theme

now it's time to make your terminal look pro just install powerlevel10k theme

git clone --depth=1 https://github.com/romkatv/powerlevel10k.git ${ZSH_CUSTOM:-$HOME/.oh-my-zsh/custom}/themes/powerlevel10k

now change the main theme on the OhMyZsh config

sudo nano ~/.zshrc

Now, searching for the theme can change it

ZSH_THEME="powerlevel10k/powerlevel10k"

now close your terminal and open it again to restart zsh and after that start your config

p10k configure

after config your theme you will see the new theme.

Generate a flutter app from your Tomato App!

Fady Mondy — Thu, 12 Oct 2023 18:16:47 +0000

as we go to make everything easy, we are today releasing a very very good package to build a flutter app by just using 1 command to generate full CRUD from your schema and generated TomatoPHP files

Requirements

please check that you have flutter installed and working on your system by check

flutter doctor

and you must have at least one emulator or device connected to your system

and you must have 2 packages working on your Laravel app Tomato Admin and Tomato CRM

after installing the package please make sure that you add a guard of accounts to your auth.php config like this

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
        'accounts' => [
            'driver' => 'session',
            'provider' => 'accounts',
        ],
    ],

...


    'providers' => [
        'users' => [
            'driver' => 'eloquent',
            'model' => App\Models\User::class,
        ],

        'accounts' => [
            'driver' => 'eloquent',
            'model' => \TomatoPHP\TomatoCrm\Models\Account::class,
        ],
    ],

Installation

composer require tomatophp/tomato-flutter

now you are ready to generate a new app

to generate a new app you just need to run this command

php artisan tomato-flutter:generate

Generate Module

to generate a new module you just need to run this command

php artisan tomato-flutter:module

Generate Controller

to generate a new controller you just need to run this command

php artisan tomato-flutter:controller

Generate Service

to generate a new service you just need to run this command

php artisan tomato-flutter:service

Generate CRUD

to generate a new CRUD from any table on your tomato-php generated CRUDs just need to run this command

php artisan tomato-flutter:crud

please note that the generated files will match only APIs generated by TomatoPHP and you need to add API routes to the api.php

Route::middleware(['auth:sanctum'])->name('api.')->group(function () {
    Route::get('customers', [\Modules\Customers\Http\Controllers\CustomerController::class, 'index'])->name('customers.index');
    Route::post('customers', [\Modules\Customers\Http\Controllers\CustomerController::class, 'store'])->name('customers.store');
    Route::get('customers/{model}', [\Modules\Customers\Http\Controllers\CustomerController::class, 'show'])->name('customers.show');
    Route::post('customers/{model}', [\Modules\Customers\Http\Controllers\CustomerController::class, 'update'])->name('customers.update');
    Route::delete('customers/{model}', [\Modules\Customers\Http\Controllers\CustomerController::class, 'destroy'])->name('customers.destroy');
});

Change Endpoint

if you like to change the endpoint to match your URL you can change it from the file

flutter/YOUR_APP/lib/config/Config.dart

and change it to your endpoint, if you are using Android you check the app please make the endpoint hit to http://10.0.2.2:8000/api and run

php artisan serv

on your app.