Codeigniter Framework
codeigniter/
├── modules/
│ ├── auth
│ ├── home
├── public/
│ ├── .htaccess
│ └── index.php
├── src/
├── vendor/
│ └── codeigniter/
│ └── framework/
│ └── system/
├── composer.json
To create MVC stack (controller, model, view) you can use create:app.
Usage example
// Create an MVC stack
composer run-script matches create:app users
// Create an MVC stack inside admin module
composer run-script matches create:app admin.users
You can use Matches to create a Controller file. The command will need at leas a parameter which represents the name of the controller.
You can put the controller inside a module. Directories are delimited with ".". So, if you want to create the controller inside modules/admin/controllers, you can do create:controller admin.name_of_controller.
Usage examples
// Create a Welcome controller
composer run-script matches create:controller welcome
// Create a User controller inside admin module
composer run-script matches create:controller admin.user
Creates a model having name_of_model as name. You can put the model inside a module. Directories are delimited with ".". So, if you want to create the model inside modules/admin/models, you can do create model admin.name_of_model.
Usage examples
// Create a user model
composer run-script matches create:model user
// Create a User model inside admin module
composer run-script matches create:model admin.user
Creates a view having name_of_view as file name. You can put the view inside a module. Directories are delimited with ".". So, if you want to create the view inside modules/admin/views, you can do create view admin.name_of_view.
Usage examples
// Create an index_view.php
composer run-script matches create:view user_view
// Create an index_view.php inside users module
composer run-script matches create:view users.index_view
CodeIgniter Matches helps you create, do, undo, and reset migrations.
To create a migration you can call create:migration. As a result, a migration will be created in the migrations directory prefixed with version as file name. You can also pass a table name as parameter. If no table name is given, you will have to put the name of the table in the migration file. Below are usage examples:
Usage examples
// Create a migration
composer run-script matches create:migration create_users_table
// Create a migration with a table inside it
composer run-script matches create:migration create_users_table table:users
// Create a migration with a table inside it
composer run-script matches create:migration create_users_table t:users
do:migration executes the migrations' up() methods. If you pass the version of the migration a parameter, it will stop at that version of the migration.
Usage examples:
// Execute all migrations until the last one
composer run-script matches do:migration
// Execute all migrations until a certain version of migration
composer run-script matches do:migration 20150722
undo:migration returns you to the previous migration version. This one also can accept a migration version as parameter to return to a migration.
Usage examples:
// Undo last migration
composer run-script matches undo:migration
// Undo the migrations until a specified migration version
composer run-script matches undo:migration 20150722
reset:migration will reset the migrations until the migration mentioned in $config['migration_version'] (in the migration configuration file).
Usage example:
// Reset the migrations
composer run-script matches reset:migration