### Docker Setup and Initial Configuration Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Commands to set up the Docker environment, install dependencies, and run initial project setup. ```bash docker compose up -d --build docker exec ci4ms_app composer install docker exec ci4ms_app php spark ci4ms:setup ``` -------------------------------- ### Automated CLI Installation with ci4ms:setup Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md This command automates the entire installation process, including database setup, seeding, and user creation. It's ideal for CI/CD pipelines. ```bash php spark ci4ms:setup --all ``` -------------------------------- ### Docker Environment Setup Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Initial setup steps for Docker-based development, including copying the environment file and preparing routes. ```bash cp env .env cp app/Config/DefaultRoutes.php app/Config/Routes.php ``` -------------------------------- ### Set Up Environment File Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Copy the example environment file to `.env` and update necessary configurations like `app.baseURL` and database credentials. ```bash cp env .env ``` -------------------------------- ### Run One-Command Setup Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Execute the `ci4ms:setup` spark command to run all migrations, seed default data, and prepare the application. ```bash php spark ci4ms:setup ``` -------------------------------- ### Clone and Install Dependencies Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Clone the repository and install PHP dependencies using Composer. Ensure you have Composer 2.5+ installed. ```bash git clone ci4ms cd ci4ms composer install ``` -------------------------------- ### Serve Application Locally Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Start the local development server using the CodeIgniter spark command. ```bash php spark serve ``` -------------------------------- ### Scaffold a New Module with ci4ms:make:module Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md Use this command to generate a new module skeleton within the application. Ensure the 'ci4-cms-erp/ext_module_generator' package is installed. ```bash php spark make:module Foo ``` -------------------------------- ### Prepare Routes Configuration Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Copy the default routes configuration to `Routes.php` to set up routing for the application. ```bash cp app/Config/DefaultRoutes.php app/Config/Routes.php ``` -------------------------------- ### Generate Backend View from AdminLTE Template with Spark Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md Creates a backend view file using the AdminLTE template. Replace `` with the view name. ```bash php spark make:abview ``` -------------------------------- ### Scaffold a New Module Skeleton with Spark Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md Generates the basic file structure for a new module. Replace `` with your desired module name. ```bash php spark make:module ``` -------------------------------- ### Rebuild Routes File with Spark Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md Updates the `app/Config/Routes.php` file based on the defined template. Useful after significant route changes. ```bash php spark create:route ``` -------------------------------- ### Module Scaffolding Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Command to scaffold a new module using the provided generator. ```bash php spark make:module ``` -------------------------------- ### Composer Dependency Management Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Commands for managing project dependencies using Composer. ```bash composer install ``` ```bash composer update vendor/package ``` ```bash composer outdated ``` -------------------------------- ### Theme Registration with info.xml Source: https://ci4-cms-erp.github.io/ci4ms/theme_development.html This XML file registers your theme with the CI4MS administrative panel. Ensure the slug matches your theme's folder name. ```xml Starter Theme starter Your Identity starter/screenshot.png 1.0.0 Your theme specification ``` -------------------------------- ### Run All Pending Migrations with Spark Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md Executes all database migrations that have not yet been applied. ```bash php spark migrate --all ``` -------------------------------- ### Clearing Cache Source: https://ci4-cms-erp.github.io/ci4ms/developer-handbook.html Commands to clear application caches, including permissions and general settings. ```bash php spark cache:clear ``` ```php cache()->delete("{userId}_permissions") ``` ```php cache()->delete('settings') ``` -------------------------------- ### Clear All Caches Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md Use this command to clear all cached data. Alternatively, individual keys can be deleted using the cache() function. ```bash php spark cache:clear ``` -------------------------------- ### Echoing Content in base.php Layout Source: https://ci4-cms-erp.github.io/ci4ms/theme_development.html The master HTML layout file for your theme. You must echo the $content variable within the body element to render page-specific output. ```html
``` -------------------------------- ### Configure ThirdParty Directory in Paths.php Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md This configuration is required for CodeIgniter 4.4+ to correctly locate the framework's ThirdParty directory. Ensure this path is set correctly in your application's Paths.php. ```php public string $supportDirectory = __DIR__ . '/../../vendor/codeigniter4/framework/system/ThirdParty'; ``` -------------------------------- ### Delete Specific Cache Key Source: https://ci4-cms-erp.github.io/ci4ms/architecture.md This function allows for the selective deletion of a cache entry by its key. ```php cache()->delete($key); ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.