How do I install Hyn/Multi-Tenant in Laravel?

Install via Composer with `composer require hyn/multi-tenant`, then publish configurations and run migrations. The README details steps for automatic or manual service registration, including modifying config files.

Hyn/Multi-Tenant vs Spatie Laravel Multitenancy: which is better?

Hyn/Multi-Tenant focuses on event-driven architecture and web server integration for scalability, while Spatie's package is simpler and more lightweight. Choose Hyn for complex SaaS with hostname routing; Spatie for basic database separation.

Can I use Hyn/Multi-Tenant with PostgreSQL?

Yes, it supports MySQL, MariaDB, and PostgreSQL as per the requirements, but you must configure the database connections in Laravel's config files to match your setup.

How to handle tenant-specific migrations?

The package uses a system database for tenant management, and you can run tenant migrations via events or custom logic, but the README warns that testing resets databases, so plan carefully.

Is Hyn/Multi-Tenant production ready for high traffic?

Yes, with its database isolation and event-driven design, it's built for scalability, but performance depends on proper server configuration and tenant data management strategies.

How to add custom configurations per tenant?

Leverage the event-driven architecture to override configs, code, and routes per tenant, as described in the features, allowing tailored logic for each website.

Open-Awesome

Multi-tenant

MITPHP5.9.1

An unobtrusive Laravel package for multi-tenancy, enabling multiple independent websites from a single codebase with separated data.

Visit Website GitHub

2.6k stars398 forks0 contributors

What is Multi-tenant?

Hyn/Multi-Tenant is a Laravel package that enables multi-tenancy, allowing a single Laravel application to serve multiple independent websites (tenants) from the same codebase. It solves the problem of managing separate data, assets, and configurations for each tenant while keeping the application scalable and maintainable. It provides clear separation of tenant-specific data and supports various database separation strategies.

Target Audience

Laravel developers building SaaS applications, marketing agencies managing multiple client websites, or startups creating scalable multi-tenant platforms. It's also suitable for developers needing to convert an existing Laravel app into a multi-tenant system.

Value Proposition

Developers choose Hyn/Multi-Tenant for its unobtrusive integration with Laravel, event-driven extensibility, and flexible database separation options. It offers a robust, production-ready solution without forcing major architectural changes, making it easier to adopt and customize compared to building multi-tenancy from scratch.

Overview

Run multiple websites using the same Laravel installation while keeping tenant specific data separated for fully independent multi-domain setups, previously github.com/hyn/multi-tenant

Use Cases

Best For

Building SaaS platforms with isolated customer data
Marketing agencies hosting multiple client websites from one codebase
Converting an existing Laravel monolith into a multi-tenant application
Managing tenant-specific configurations and overrides in Laravel
Implementing scalable database separation strategies for multi-domain setups
Creating event-driven, extensible multi-tenant architectures

Not Ideal For

Single-tenant applications where multi-tenancy adds unnecessary complexity and overhead
Projects using microservices or serverless architectures where each tenant is deployed separately
Teams that require out-of-the-box, zero-configuration solutions without web server integration

Pros & Cons

Pros

Unobtrusive Laravel Integration

Integrates smoothly without requiring major changes to the Laravel application structure, as emphasized in the README's philosophy of staying out of the developer's way.

Event-Driven Extensibility

Built on Laravel events, allowing deep customization through event listeners, which supports flexible tenant management and overrides, as highlighted in the features.

Flexible Database Strategies

Supports multiple separation methods including isolated databases, table prefixes, or manual handling via events, catering to different scalability and isolation needs.

Web Server Optimization

Offers optional close integration with Apache or Nginx for efficient hostname routing, reducing application-level overhead for tenant identification.

Active Community Support

Backed by Discord chat, comprehensive documentation at tenancy.dev, and sponsors, indicating ongoing development and assistance for users.

Cons

Configuration Complexity

Requires manual setup steps like publishing configurations, modifying files, and managing system database migrations, which can be time-consuming and error-prone.

Webserver Dependency

Tight integration with Apache or Nginx limits usage in environments with other servers or serverless setups, as noted in the requirements.

Potential Breaking Changes

With multiple versions (e.g., 5.x) and a changelog, updates might introduce breaking changes, requiring careful migration and testing.

Frequently Asked Questions

Related Projects

LiveWire

A full-stack framework for Laravel that takes the pain out of building dynamic UIs.

Debugbar for Laravel (Integrates PHP Debug Bar)

Stars19,179

Forks1,607

Last commit2 days ago

IDE Helper

IDE Helper for Laravel

Stars14,891

Forks1,188

Last commit23 days ago

Intervention Image

PHP Image Processing

Stars14,330

Forks1,491

Last commit5 days ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub