Krud configuration wizard

Multi-tenant Configuration

At the beginning of the wizard, KituKizuri asks whether the application should be configured as a multi-tenant system.

• Yes — Enables multi-tenant behavior and prepares the project to isolate data and configuration per tenant.
• No — Keeps the application as a standard single-tenant setup, using a single shared configuration.

This decision defines how KituKizuri will generate the initial structure and runtime configuration for the project. If you are building a platform where multiple organizations, clients, or environments must operate independently within the same application, enabling multi-tenancy is recommended.

You can proceed with the wizard after selecting the option that matches your project requirements.

LDAP Authentication

In this step, the wizard asks whether the application should enable authentication via LDAP.

• Yes — Enables LDAP-based authentication, allowing users to log in using credentials managed by an external directory service such as Active Directory.
• No — Uses the default authentication mechanism provided by the application.

When LDAP authentication is enabled, KituKizuri prepares the necessary configuration to integrate the application with an LDAP directory, making it suitable for corporate and enterprise environments where centralized identity management is required.

This option is completely optional and can be skipped if LDAP integration is not needed for the project.

Vue Integration

In this step, the wizard asks whether Vue should be configured as part of the application frontend.

• Yes — Enables Vue integration and prepares the project structure to support reactive user interfaces and frontend components.
• No — Keeps the application using a server-rendered approach without additional frontend framework setup.

When enabled, KituKizuri configures the necessary assets and dependencies to allow seamless use of Vue within the Laravel project, without forcing architectural decisions. This option is ideal for projects that require dynamic or interactive user interfaces.

You can proceed with or skip this integration based on the frontend needs of your application.

React Integration

In this step, the wizard asks whether React should be configured as part of the application frontend.

• Yes — Enables React integration and prepares the project to support component-based frontend development.
• No — Skips React setup and keeps the existing frontend configuration unchanged.

KituKizuri allows Vue and React to coexist within the same project if both options are enabled. While this level of flexibility is supported, using multiple frontend frameworks in a single application is generally not recommended unless there is a clear architectural reason to do so.

This option is provided to support advanced or transitional use cases where multiple frontend technologies are required.

MongoDB Integration

In this step, the wizard asks whether MongoDB support should be enabled for the application.

• Yes — Installs and configures the required packages to allow MongoDB to be used alongside Laravel, including support for working with MongoDB using Eloquent-style models.
• No — Skips MongoDB integration and keeps the application configured for relational databases only.

When enabled, KituKizuri prepares the project to work with MongoDB as a complementary data store, making it suitable for hybrid data scenarios where both relational and document-based models are required.

This step focuses on application-level integration, not database provisioning.

Database Logging

In this step, the wizard asks whether application logs should be stored in the database.

• Yes — Enables database-backed logging, allowing application events and errors to be persisted for auditing, troubleshooting, and historical analysis.
• No — Uses the default logging configuration without database storage.

When enabled, KituKizuri configures the necessary components to record logs in the database, making them accessible for administrative review and operational monitoring.

This option is particularly useful for environments where centralized log visibility or long-term traceability is required.