寻求CodeIgniter多租户应用开发的资源与经验分享

Hey there! I’ve built a couple of multi-tenant apps with CodeIgniter using the single-database, single-codebase approach, so I can share some solid insights and resources to get you started.

• CodeIgniter Official Docs + Community Forums: While the official docs don’t have a dedicated multi-tenant guide, their sections on database classes, hooks, and core extensions are foundational. Head to the CodeIgniter community forums and search for "multi-tenant single database"—you’ll find tons of user-shared implementations, troubleshooting tips, and discussions around tenant isolation logic.
• Practical Blog Tutorials: Several developers have written step-by-step walkthroughs for this exact setup. Look for posts covering:
  • Injecting tenant context via base controllers or hooks
  • Modifying database tables to include tenant identifiers
  • Automating query filtering across models
• Open-Source Examples: Search GitHub for "CodeIgniter multi tenant single database" to find small, functional projects (like mini CRMs or CMS tools) that implement this pattern. Clone them to study how they handle routing, tenant identification, and data isolation—real code is often the best teacher.

These are the key practices I’ve found most useful for maintaining a clean, secure multi-tenant CodeIgniter app:

• Base Controller for Tenant Context: Create a MY_Controller (CodeIgniter’s standard way to extend core controllers) that runs in every request. In its constructor, fetch the current tenant ID (from a logged-in user’s session, subdomain, or request header) and store it as a class property. All your business controllers inherit this base class, so tenant context is available everywhere.
• Auto-Filtered Models: Extend CodeIgniter’s base Model into a MY_Model that automatically adds tenant_id filters to all queries. For example:

  class MY_Model extends \CodeIgniter\Model
  {
      protected function getCurrentTenantId()
      {
          return session()->get('tenant_id');
      }
  
      public function get($where = null, $limit = null, $offset = 0)
      {
          $this->db->where('tenant_id', $this->getCurrentTenantId());
          return parent::get($where, $limit, $offset);
      }
  
      public function insert($data = null, $returnID = true)
      {
          if (!isset($data['tenant_id'])) {
              $data['tenant_id'] = $this->getCurrentTenantId();
          }
          return parent::insert($data, $returnID);
      }
  }
  

  All models you create inherit this, so you never have to manually add tenant filters again.
• Tenant Identification Logic: If using subdomains (e.g., client1.yourapp.com), use a pre-controller hook to parse the subdomain, look up the corresponding tenant in your tenants table, and store the ID in the session. Example snippet:

  // In hooks.php
  $hook['pre_controller'][] = [
      'function' => 'setTenantContext',
      'filename' => 'TenantHook.php',
      'filepath' => 'hooks'
  ];
  
  // In hooks/TenantHook.php
  function setTenantContext()
  {
      $host = $_SERVER['HTTP_HOST'];
      $parts = explode('.', $host);
      $subdomain = $parts[0];
  
      $tenantModel = new \App\Models\TenantModel();
      $tenant = $tenantModel->where('subdomain', $subdomain)->first();
  
      if ($tenant) {
          session()->set('tenant_id', $tenant->id);
      } else {
          // Redirect to tenant registration or 404
          header('Location: /tenant-register');
          exit;
      }
  }
  

• Migration Best Practices: Every table that needs tenant isolation must include a tenant_id field. Add an index to this field to speed up filtered queries. Example migration:

  public function up()
  {
      $this->forge->addField([
          'id' => [
              'type' => 'INT',
              'constraint' => 11,
              'unsigned' => true,
              'auto_increment' => true,
          ],
          'tenant_id' => [
              'type' => 'INT',
              'constraint' => 11,
              'unsigned' => true,
          ],
          // Your other fields here
      ]);
      $this->forge->addKey('id', true);
      $this->forge->addKey('tenant_id');
      $this->forge->createTable('products');
  }
  

• Security Guardrails: Never trust user input for tenant_id—force it in your model’s insert/update methods (like the MY_Model example above) to prevent cross-tenant data access. Also, add a check in your base controller to ensure the logged-in user belongs to the current tenant ID.

Start small by testing the tenant filtering logic on a single table (like users or products) before expanding to your entire app. Once the base setup is solid, scaling becomes much easier!

内容的提问来源于stack exchange，提问作者Avnsai