mirror of
https://github.com/archtechx/tenancy.git
synced 2025-12-12 14:54:04 +00:00
Add CLAUDE.md
This commit is contained in:
parent
588d1fcc0d
commit
37f6260812
1 changed files with 97 additions and 0 deletions
97
CLAUDE.md
Normal file
97
CLAUDE.md
Normal file
|
|
@ -0,0 +1,97 @@
|
|||
# CLAUDE.md
|
||||
|
||||
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
|
||||
|
||||
## Development Commands
|
||||
|
||||
### Testing
|
||||
- `composer test` - Run tests without coverage using Docker
|
||||
- `./t 'test name'` - Run a specific test
|
||||
|
||||
### Code Quality
|
||||
- `composer phpstan` - Run PHPStan static analysis (level 8)
|
||||
- `composer cs` - Fix code style using PHP CS Fixer
|
||||
|
||||
### Docker Development
|
||||
- `composer docker-up` - Start Docker environment
|
||||
- `composer docker-down` - Stop Docker environment
|
||||
- `composer docker-restart` - Restart Docker environment
|
||||
|
||||
## Architecture Overview
|
||||
|
||||
**Tenancy for Laravel** is a multi-tenancy package that automatically handles tenant isolation without requiring changes to application code.
|
||||
|
||||
### Core Components
|
||||
|
||||
**Central Classes:**
|
||||
- `Tenancy` - Main orchestrator class managing tenant context and lifecycle
|
||||
- `TenancyServiceProvider` (NOT the stub) - Registers services, commands, and bootstrappers
|
||||
- `Tenant` (model) - Represents individual tenants with domains and databases
|
||||
- `Domain` (model) - Maps domains/subdomains to tenants
|
||||
|
||||
**Tenant Identification:**
|
||||
- **Resolvers** (`src/Resolvers/`) - Identify tenants by domain, path, or request data - this data comes from middleware
|
||||
- **Middleware** (`src/Middleware/`) - Middleware that calls resolvers and tries to initialize tenancy based on information from a request
|
||||
- **Cached resolvers** - Cached wrapper around resolvers to avoid querying the central database
|
||||
|
||||
**Tenancy Bootstrappers (`src/Bootstrappers/`):**
|
||||
- `DatabaseTenancyBootstrapper` - Switches database connections
|
||||
- `CacheTenancyBootstrapper` - Isolates cache by tenant
|
||||
- `FilesystemTenancyBootstrapper` - Manages tenant-specific storage
|
||||
- `QueueTenancyBootstrapper` - Ensures queued jobs run in correct tenant context
|
||||
- `RedisTenancyBootstrapper` - Prefixes Redis keys by tenant
|
||||
|
||||
**Database Management:**
|
||||
- **DatabaseManager** - Creates/deletes tenant databases and users
|
||||
- **TenantDatabaseManagers** - Database-specific implementations (MySQL, PostgreSQL, SQLite, SQL Server)
|
||||
- **Row Level Security (RLS)** - PostgreSQL-based tenant isolation using policies
|
||||
|
||||
**Advanced Features:**
|
||||
- **Resource Syncing** - Sync central models to tenant databases
|
||||
- **User Impersonation** - Admin access to tenant contexts
|
||||
- **Cross-domain redirects** - Handle multi-domain tenant setups
|
||||
- **Telescope integration** - Tag entries by tenant
|
||||
|
||||
### Key Patterns
|
||||
|
||||
**Tenant Context Management:**
|
||||
```php
|
||||
tenancy()->initialize($tenant); // Switch to tenant
|
||||
tenancy()->run($tenant, $callback); // Atomic tenant execution
|
||||
tenancy()->runForMultiple($tenants, $callback); // Batch operations
|
||||
tenancy()->central($callback); // Run in central context
|
||||
```
|
||||
|
||||
**Tenant Identification Flow:**
|
||||
1. Middleware identifies tenant from request (domain/subdomain/path)
|
||||
2. Resolver fetches tenant model from identification data
|
||||
3. Tenancy initializes and bootstrappers configure tenant context
|
||||
4. Application runs with tenant-specific database/cache/storage
|
||||
|
||||
**Route Middleware Groups:**
|
||||
All of these work as flags, i.e. middleware groups that are empty arrays with a purely semantic use.
|
||||
- `tenant` - Routes requiring tenant context
|
||||
- `central` - Routes for central/admin functionality
|
||||
- `universal` - Routes working in both contexts
|
||||
- `clone` - Tells route cloning logic to clone the route
|
||||
|
||||
### Testing Environment
|
||||
|
||||
Tests use Docker with MySQL/PostgreSQL/Redis. The `./test` script runs Pest tests inside containers with proper database isolation.
|
||||
|
||||
`./t 'test name'` is equivalent to `./test --filter 'test name'`
|
||||
|
||||
**Key test patterns:**
|
||||
- Database preparation and cleanup between tests
|
||||
- Multi-database scenarios (central + tenant databases)
|
||||
- Middleware and identification testing
|
||||
- Resource syncing validation
|
||||
|
||||
### Configuration
|
||||
|
||||
Central config in `config/tenancy.php` controls:
|
||||
- Tenant/domain model classes
|
||||
- Database connection settings
|
||||
- Enabled bootstrappers and features
|
||||
- Identification middleware and resolvers
|
||||
- Cache and storage prefixes
|
||||
Loading…
Add table
Add a link
Reference in a new issue