<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/vendor/feed/atom.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-US">
                        <id>https://laravel.io/index.php/forum/feed</id>
                                <link href="https://laravel.io/index.php/forum/feed" rel="self"></link>
                                <title><![CDATA[Laravel.io Forum RSS Feed]]></title>
                    
                                <subtitle>The RSS feed for the Laravel.io forum contains a list of all threads posted by community members.</subtitle>
                                                    <updated>2026-07-31T02:57:32+00:00</updated>
                        <entry>
            <title><![CDATA[Sofware Development Company in Dubai]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/sofware-development-company-in-dubai" />
            <id>https://laravel.io/index.php/30852</id>
            <author>
                <name><![CDATA[Joshika]]></name>
            </author>
            <summary type="html">
                <![CDATA[Techanic Infotech 
Dubai-based software development company offering mobile app, web, custom software, and AI development services. Team of 70+ in-house engineers, founded in 2020, with 730+ clients delivered across 40+ countries. Services include Android/iOS app development, cross-platform apps (Flutter, React Native), AI/ML and generative AI solutions, custom enterprise software, and ongoing maintenance/support. Office located on Sheikh Zayed Road, Dubai. Rated 4.9/5 on Clutch and 4.8/5 on GoodFirms.

Website: [https://www.techanicinfotech.ae/](https://www.techanicinfotech.ae/)]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Swagger alternatives for Laravel APIs in 2026cc]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/swagger-alternatives-for-laravel-apis-in-2026cc" />
            <id>https://laravel.io/index.php/30851</id>
            <author>
                <name><![CDATA[luc]]></name>
            </author>
            <summary type="html">
                <![CDATA[I've been working on Laravel API projects and recently started reviewing our API documentation workflow.

Swagger/OpenAPI tools have been useful for generating documentation, but as projects grow, we're looking for a workflow that covers more than just documentation.

Some things we're interested in:

OpenAPI specification management
API documentation generation
API testing
Mocking during development
Keeping docs synchronized with Laravel code changes
CI/CD integration

For Laravel applications, especially those exposing REST APIs with tools like Sanctum or Passport, maintaining accurate API documentation can become challenging as endpoints evolve.

I'm curious how other Laravel developers are handling this today:

Are you still using Swagger/OpenAPI tools?
Have you moved to any Swagger alternatives?
Do you prefer separate tools for documentation and testing, or an all-in-one API platform?
How are you keeping your API docs updated as your Laravel application changes?

Would love to hear what workflows and tools are working well for the community.]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Laravel, Healthcare Compliance and More]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/laravel-healthcare-compliance-and-more" />
            <id>https://laravel.io/index.php/30849</id>
            <author>
                <name><![CDATA[banks]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hi I am pretty new at laravel and is quite impressed with the massive support in terms of tech stack and more. I am a business analyst with some little experience in coding, i have always been a wordpress person but really impressed with the creativity laravel brings.
I am working as a development manager for a UK home care business and just built out (with claude - yes vieb coded somewhat) a healthcare compliance web app with PWA support for carers when they visit client homes. We chose not to go the route of mobile app because of the cost and risks to data and aditional infra requirements which the business cannot afford. Hosted in laravel cloud and guarded by laravel sentry, i want to know if anyone has issues around compliance as i have noticed that the compliance bit is even more work than building out the code base.
I also expected laravel cloud would have some documentation i could use to build out my business continuity policies and those related to healthcare compliance.
All help will be appreciated.]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[I said goodbye to Queues and Horizon]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/i-said-goodbye-to-queues-and-horizon" />
            <id>https://laravel.io/index.php/30848</id>
            <author>
                <name><![CDATA[Krvin]]></name>
            </author>
            <summary type="html">
                <![CDATA[I replaced our Queue/Horizon tier with a database-backed job engine; now stable, feedback welcome

Background:  I run a fairly large Queue/Horizon implementation (six-figure job counts, multi-host workers, nightly batch DAGs hundreds of jobs wide), and I kept hitting the same architectural wall: once a job is handed to a worker, the system can't tell you which process is running it, whether that process is still alive, or whether it's safe to retry. Everything is inferred from timeouts. When a host died mid-batch, healing a complex chain of dependent jobs was effectively impossible — orphaned members, blind retries of non-idempotent work, no audit trail.

So I rolled my own. After ten public betas running our entire production background tier, I've cut a stable release and would love eyes on it:

**JobWarden** — https://github.com/kpconnell/laravel-jobwarden

The summary: the system knows at all times what is running where, and recovers from infrastructure failure using verified process liveness — not timeouts.

- Database-backed (no Redis): jobs, attempts, logs, results, and audit events are durable SQL rows
- Every attempt runs in its own child process, stamped with host / PID / start time / fencing token
- Non-idempotent jobs are never blindly re-run — lost work parks for an operator instead
- Batches: fan-out, chains, and arbitrary DAGs with failure policies; retrying a failed upstream revives the dependents that were canceled downstream
- Scheduling that handles overlaps and missed cron ticks the way you'd expect, with run history
- Livewire operator console + JSON API (screenshots in the README)

![A 239-node production batch DAG](https://raw.githubusercontent.com/kpconnell/laravel-jobwarden/main/docs/images/dashboard-batch-dag.png)

Fair warning on requirements: PHP 8.3+, Laravel 11/12, Linux only (it leans on `pcntl` and `/proc` — that's where the process-identity guarantees come from).

I'd particularly value feedback on the job-authoring API (constructor param binding, method-injected `handle()`) and on whether the docs make the recovery model clear. Happy to answer anything about the internals — the fencing/orphan-detection design was the hard part.


[Laravel JobWarden](https://github.com/kpconnell/laravel-jobwarden)

![](https://github.com/kpconnell/laravel-jobwarden/raw/main/docs/images/dashboard-overview.png)]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Released Laravel Cooldown: A Driver-Based Cooldown Manager]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/released-laravel-cooldown-a-driver-based-cooldown-manager" />
            <id>https://laravel.io/index.php/30843</id>
            <author>
                <name><![CDATA[Mahedi Zaman Zaber]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hi everyone! 👋

I've just open-sourced **Laravel Cooldown**, a package for managing **action cooldowns** in Laravel.

While Laravel's built-in `RateLimiter` is excellent for request throttling, I found myself repeatedly needing a reusable solution for **time-based action restrictions**, such as:

* Password reset requests
* Email verification
* OTP / SMS sending
* AI prompt generation
* Report exports
* Payment retries
* Reward claiming
* Other workflow-based cooldowns

My goals were to make it:

* Driver-based (Cache & Database)
* Easy to attach to Eloquent models
* Middleware-friendly
* Extensible with custom storage drivers
* Pleasant to use through a fluent API

Example:

```php
Cooldown::for('password_reset', $user)->enforce();

// Perform the action...

Cooldown::for('password_reset', $user)->for(300);
```

Some features include:

* Cache & Database drivers
* Native Eloquent integration (`HasCooldowns`)
* Route middleware
* Success-only cooldown triggering (only starts after successful 2xx/3xx responses)
* Immutable DTOs
* Event dispatching
* Automatic database pruning
* Custom driver support via `Cooldown::extend()`

One design decision I'm particularly interested in feedback on is the middleware behavior. Instead of starting the cooldown before the request executes, it only creates the cooldown after a successful response. That way, validation errors or failed requests don't unnecessarily lock users out.

I'd really appreciate any feedback on the API, architecture, naming, or overall developer experience. Suggestions for additional drivers or features are also very welcome.

Repository:
https://github.com/zaber-dev/laravel-cooldown

Thanks!]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Open-Source Textile ERP Built with Next.js 16]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/open-source-textile-erp-built-with-nextjs-16" />
            <id>https://laravel.io/index.php/30841</id>
            <author>
                <name><![CDATA[Imran Dev BD]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hey everyone,

I recently built an open-source Textile ERP system and wanted to share it with the community here. While this is built entirely in the Next.js ecosystem, I know a lot of us use React/Next.js alongside our typical backend stacks, so I thought it might be of interest or serve as a good frontend architecture reference!

It's designed to handle standard ERP operations tailored specifically for the textile industry. 

**The Tech Stack:**
*   **Framework:** Next.js 16
*   **Styling:** Tailwind CSS
*   **Database/ORM:** Prisma

**Repository:**
https://github.com/imranbru99/textile-erp-nextjs

I would love for you to check it out. Feedback, code reviews, and PRs are more than welcome. If you find it useful or interesting as a reference for your own full-stack projects, a star on the repo would be highly appreciated. 

Let me know what you think of the structure or if you have any suggestions for improvement!]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[I built an Eloquent-style ORM for Node.js]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/i-built-an-eloquent-style-orm-for-nodejs" />
            <id>https://laravel.io/index.php/30840</id>
            <author>
                <name><![CDATA[Raphael Abayomi]]></name>
            </author>
            <summary type="html">
                <![CDATA[Been writing Laravel for years. Every time a project pulls me into Node.js territory, whether it's a side project, a microservice, or just helping a team, the first thing I notice is that nothing feels like Eloquent.

Prisma is fine but it's a different mental model entirely. TypeORM is verbose. Drizzle is SQL-first in a way that's almost too raw. None of them have scopes, observers, morph relationships, or that clean fluent API that just *clicks* once you know it.

So I built one.

It's called **IlanaORM** (`ilana-orm` on npm). It runs on Node.js and TypeScript, built on Knex.js under the hood, and the API is as close to Eloquent as I could get it.

Here's what the same pattern looks like side by side:

**Laravel Eloquent:**
```php
$posts = Post::published()
    ->with('author')
    ->orderBy('created_at', 'desc')
    ->get();
```

**IlanaORM:**
```ts
const posts = await Post.query()
  .published()
  .with('author')
  .orderBy('created_at', 'desc')
  .get();
```

Scopes work exactly the same way. Define them on the model, chain them on queries. Relationships (`hasOne`, `hasMany`, `belongsTo`, `belongsToMany`, `morphTo`, `morphMany`, `hasManyThrough`) all work. Soft deletes, casting, events, observers, global scopes, factories, seeders, migrations, all in there.

A few things beyond standard Eloquent:

- **ULID and UUID primary keys** supported (opt-in)
- **pgvector support** built in for AI/embedding search
- **Edge runtime support** (Cloudflare Workers, Next.js edge routes)
- Supports MySQL, PostgreSQL, SQLite, and Supabase
- No code generation step

It is live now. Docs are at https://raphwebb.mintlify.com and the package is `npm install ilana-orm`.

GitHub: https://github.com/raphyabak/ilana-orm

Genuinely curious what you all think, especially if you've worked in both Laravel and Node.js and felt the same frustration. Happy to hear what's missing or what I got wrong.]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Anti-Swagger]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/anti-swagger" />
            <id>https://laravel.io/index.php/30805</id>
            <author>
                <name><![CDATA[Myat Kyaw Thu]]></name>
            </author>
            <summary type="html">
                <![CDATA[If you’re a **Laravel developer**, you know the pain: you finish a feature, but then you spend another 30 minutes updating YAML files or adding messy docblock annotations just so the frontend team knows how the API works.

I built **Laravel API Visibility** to change that. No annotations, no configuration, and zero manual work.
What it does:
✅ Automatic Documentation: Scans your routes and controllers instantly.
✅ Static Analysis: Uses PHP Reflection to "read" your code and predict responses without even running an HTTP request.
✅ Postman Export: One click to generate a full Postman collection, pre-wired with headers and auth.
✅ FormRequest Support: Automatically detects your validation rules and generates example payloads.

It’s lightweight, dark-mode friendly, and stays out of your production environment by default.

Check it out on GitHub: https://github.com/myat-kyaw-thu/laravel-api-visibility

I'd love to hear what the Laravel community thinks!]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Can you share some real websites using Laravel]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/can-you-share-some-real-websites-using-laravel" />
            <id>https://laravel.io/index.php/30798</id>
            <author>
                <name><![CDATA[Serena]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hi Guys,

Good day! 

Can you share some real websites using Laravel? 

And If I have a website, how do I know if there's any tags or signs that shows it's using Laravel? AI tells me to check like this document.cookie.includes('laravel_session')  to see if such a cookie...is that true?

Thanks:)]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Live Browser Updates for Blade Without Livewire]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/live-browser-updates-for-blade-without-livewire" />
            <id>https://laravel.io/index.php/30838</id>
            <author>
                <name><![CDATA[Vishnu Prasad]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hi everyone,

I've been building **KAAL Realtime**, a Laravel package that enables **live updates across connected browsers** while letting you continue using standard Blade templates.

![](https://camo.githubusercontent.com/6e2dc119929c76753e737a14af94fb8129c55d13c8b54aa16f4a92e2eafd778b/68747470733a2f2f646f63732e6b61616c7265616c74696d652e636f6d2f6173736574732f6c6f676f2f6c6f676f2e706e67)

Instead of converting pages into Livewire components, you wrap the section you want to keep synchronized:

```blade
@realtime([\App\Models\Message::class])
    @include('chat.messages')
@endrealtime
```

When the underlying model changes, every connected browser viewing that page automatically receives the updated HTML fragment over WebSockets. Only the affected section is refreshed—there's no full page reload.

### Features

* Live browser-to-browser updates
* Native Blade support
* No Livewire components required
* Automatic model watching
* Handler mode for complex updates
* Signed fragment requests
* Authentication preserved
* Laravel Reverb integration
* Lightweight JavaScript runtime

For scenarios where updates depend on multiple models or custom business logic, you can also register a custom realtime handler instead of relying on automatic model detection.

Some use cases include:

* Live chat
* Notifications
* Admin dashboards
* Order management
* Inventory updates
* Support dashboards
* Monitoring panels
* Collaborative internal tools

The goal is to bring realtime capabilities to existing Blade applications with minimal changes while preserving the familiar Laravel development experience.

I'd love to hear your thoughts:

* Would you use this in a production Blade application?
* What features or integrations would you like to see?
* Are there any edge cases or performance concerns I should consider?

**Documentation:** https://docs.kaalrealtime.com

**GitHub:** https://github.com/esagono-teq/kaal-realtime.git]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[CarvePHP alpha: service boundaries in Laravel monolithsPacka]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/carvephp-alpha-service-boundaries-in-laravel-monolithspacka" />
            <id>https://laravel.io/index.php/30837</id>
            <author>
                <name><![CDATA[Muhammad Waleed Khalil]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hey everyone,

I recently released the first alpha of **CarvePHP**, an open-source Laravel package for teams working with large Laravel monoliths.

The goal is not automatic “one-click microservices.” I know that is not realistic for most real-world systems.

Instead, CarvePHP focuses on a more practical problem:

**How do you identify possible service boundaries in a Laravel monolith using evidence?**

Current alpha features:

* scans routes, controllers, models, migrations, and database usage
* optionally traces runtime route/table coupling
* builds a dependency graph
* suggests candidate service boundaries
* generates Markdown/JSON migration reports

Install:

```bash
composer require carvephp/carve:^0.1@alpha --dev
```

Basic usage:

```bash
php artisan carve:install
php artisan carve:doctor
php artisan carve:scan --pretty
php artisan carve:analyze
php artisan carve:boundaries --report=carve-boundaries.md
php artisan carve:report --output=carve-report.md
```

GitHub:
https://github.com/Muhammad-Waleed-Khalil/CarvePHP

Packagist:
https://packagist.org/packages/carvephp/carve

It currently supports Laravel 11, 12, and 13.

I’m mainly looking for feedback from Laravel developers who have worked on large monoliths:

* What evidence would you want before trusting a suggested service boundary?
* Which Laravel patterns should the analyzer support first?
* Would graph visualization, better FormRequest analysis, or API Resource analysis be more useful for the next release?

Any feedback, criticism, or real-world edge cases would be appreciated.]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Laravel Query Filters Package – Clean Eloquent filtering]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/laravel-query-filters-package-clean-eloquent-filtering" />
            <id>https://laravel.io/index.php/30836</id>
            <author>
                <name><![CDATA[Ahmed Ezz]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hey everyone 👋

I built a small Laravel package for filtering Eloquent models via request query strings, and I'd love to get some feedback from the community.

**Package:** https://github.com/AhmedEzz20/laravel-query-filters
**Packagist:** https://packagist.org/packages/dev-astro/laravel-query-filters

---

### What it does

Keeps your controllers clean by moving all filter logic into dedicated filter classes.

```bash
php artisan make:filter BrandFilter
```

```php
class BrandFilter extends BaseFilters
{
    protected array $filters = ['search_name', 'status', 'created_from'];
    protected array $sortable = ['id', 'name', 'created_at'];

    protected function searchName($value)
    {
        return $this->builder->where('name', 'like', "%{$value}%");
    }
}
```

Then in your controller:
```php
Brand::filter()->paginate();
```

---

### Features
- `make:filter` Artisan command
- Auto date range filtering via `_from` / `_to` convention
- Built-in sorting with column whitelist
- `perPage` support from request
- Zero config — works out of the box

Would love any feedback, suggestions, or PRs! 🙏]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[What do you use to compare different versions of text?]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/what-do-you-use-to-compare-different-versions-of-text" />
            <id>https://laravel.io/index.php/30835</id>
            <author>
                <name><![CDATA[Hardik Barvaliya]]></name>
            </author>
            <summary type="html">
                <![CDATA[I often need to compare different versions of documentation, website content, configuration snippets, and notes. Git works great for source code, but for plain text I sometimes find it more convenient to use a dedicated comparison tool.

I'm interested in learning what other developers use for this workflow. Do you rely on editor features, standalone applications, or browser-based tools?

Recently I came across a tool called [Text Differ](https://text-differ.com/) that focuses on comparing two blocks of text and highlighting the changes. It made me wonder what approaches others prefer and which features are most important when reviewing text revisions.

What does your workflow look like?]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[How do you track who really triggered model changes?]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/how-do-you-track-who-really-triggered-model-changes" />
            <id>https://laravel.io/index.php/30834</id>
            <author>
                <name><![CDATA[Roma]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hi everyone,
I’ve been running into an issue in queue-heavy Laravel apps where the real origin of a change gets lost.
Typical flow:
HTTP request → service → queue → job → model update
By the time the model is updated, the audit log usually only shows the job or system as the actor, not the user who originally triggered the action.
So instead of:
“User Roman changed the order”
you often end up with:
“System updated order”
This makes debugging incidents really hard, because you lose the execution context across the queue boundary.
I’m curious how others handle this problem, do you track origin somehow, or just rely on basic audit logs?]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Pterocos - Browser-based PHP editor for Laravel prototyping]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/pterocos-browser-based-php-editor-for-laravel-prototyping" />
            <id>https://laravel.io/index.php/30833</id>
            <author>
                <name><![CDATA[Amine. KHD]]></name>
            </author>
            <summary type="html">
                <![CDATA[Hey Laravel community!

I built Pterocos (https://pterocos.eu.org) - a free online editor that runs PHP code entirely in your browser. No installation, no account required.

**Why Laravel developers might find this useful:**
- Quickly test PHP snippets without local setup
- Prototype Laravel logic (collections, queries) instantly
- Share runnable examples with teammates or learners

**What Pterocos supports:**
- PHP 🐘
- Also: C#, Rust, Python, Ruby, SQL (SQLite/DuckDB), Lua

The editor runs entirely client-side - your code never leaves your browser.

**Try it:** https://pterocos.eu.org

Would love feedback from the Laravel community!]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[ERP Software Development Company | Enterprise Resource Plann]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/erp-software-development-company-enterprise-resource-plann" />
            <id>https://laravel.io/index.php/30832</id>
            <author>
                <name><![CDATA[jafijanet]]></name>
            </author>
            <summary type="html">
                <![CDATA[As a trusted [](https://www.nxdeep.com/erp-software-development), NxDeep Connectz creates strong and scalable ERP solutions designed for specific business needs. Our ERP systems bring together essential business processes, remove data silos, and improve operational efficiency through centralized management and real-time analytics. We assist organizations with custom ERP development, implementation, integration, and ongoing support. Our goal is to help businesses use resources more effectively, streamline workflows, and boost growth with secure and future-ready ERP software solutions.
![]()]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Is it correct to use ASSET_URL or forceRootUrl() when behind]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/is-it-correct-to-use-asset-url-or-forcerooturl-when-behind" />
            <id>https://laravel.io/index.php/30829</id>
            <author>
                <name><![CDATA[Tarcísio Santos]]></name>
            </author>
            <summary type="html">
                <![CDATA[I'm using Laravel 13 and accessing my app via ngrok. I noticed that changing APP_URL in my .env file doesn't affect asset() it still generates localhost URLs. After digging in, I found two ways to fix it:

1. Set ASSET_URL to the ngrok URL
2. Add URL::forceRootUrl(config('app.url')) in AppServiceProvider::boot()

Both work, but the docs say ASSET_URL is intended for CDN deployments where assets are on a separate domain. And forceRootUrl() feels heavy since it overrides all URL generation.
My question is: what's the correct approach for a scenario like this (ngrok, or even a real hosting behind a proxy)? Should I always set ASSET_URL alongside APP_URL in these environments, or is forceRootUrl() the intended way to make APP_URL control all generated URLs?]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Advice/tips on a React application with Laravel backend]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/advicetips-on-a-react-application-with-laravel-backend" />
            <id>https://laravel.io/index.php/30828</id>
            <author>
                <name><![CDATA[Ginus van der Zee]]></name>
            </author>
            <summary type="html">
                <![CDATA[I'm currently working on a personal project related to Warhammer. Because I needed to test some things, I have made an test project for a quiz that would help select a faction. But I'm kind of still looking for advise to improve it. 

At first I had all the faction calculations run on the backend, but I've since moved that to the frontend. I was thinking of expanding the database and have tables with Warhammer units be tied the faction and have the website showcase them.


Github link: https://github.com/GinusHR/ple-content-quiz-test]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Built a binary approval workflow engine for Laravel]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/built-a-binary-approval-workflow-engine-for-laravel" />
            <id>https://laravel.io/index.php/30826</id>
            <author>
                <name><![CDATA[mema]]></name>
            </author>
            <summary type="html">
                <![CDATA[I’ve been working on internal approval/workflow systems for years and recently tried extracting the core engine into a reusable Laravel package.

Repository:
[Approval Binary GitHub Repository](https://github.com/menma977/Approval-Binary)

The package started as a simple approval system idea but eventually evolved into something closer to a workflow orchestration engine.

Main concepts currently implemented:

sequential & parallel approval
AND / OR contributor logic
dynamic approver resolution
condition-based routing
runtime event snapshots
rollback / force state handling
bigint bitmask approval state

The binary/bitmask idea was inspired by Linux permission concepts to represent partial approval states without relying only on status columns or linear step numbers.

One thing I’m still unsure about is whether this abstraction level still makes sense inside Laravel ecosystem, or if I’m overengineering something that most applications would solve with simpler patterns.

I’d really appreciate feedback from people who have experience with:

approval engines
ERP/internal systems
workflow orchestration
backend-heavy architecture
state modeling

Especially interested in opinions about:

architecture direction
workflow modeling
bitmask state approach
possible edge cases
maintainability concerns

Would love honest criticism.]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Laravel Tailwind tables (like Yajra, no Livewire)]]></title>
            <link rel="alternate" href="https://laravel.io/index.php/forum/laravel-tailwind-tables-like-yajra-no-livewire" />
            <id>https://laravel.io/index.php/30789</id>
            <author>
                <name><![CDATA[Tarcísio Santos]]></name>
            </author>
            <summary type="html">
                <![CDATA[Good evening, everyone!
I’m looking for recommendations for libraries or packages to create tables in Laravel using Tailwind CSS. Previously, I used Yajra Laravel DataTables with Bootstrap, but now I want to switch to a solution that works well with Tailwind and, preferably, doesn’t rely on Livewire.
Does anyone have suggestions for packages or approaches that can replace Yajra while keeping pagination, sorting, and filtering functionality?
Thanks!]]>
            </summary>
                                    <updated>2026-07-31T02:57:32+00:00</updated>
        </entry>
    </feed>
