Download the PHP package laragear/meta-model without Composer
On this page you can find all versions of the php package laragear/meta-model. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package meta-model
Meta Model
Let other developers customize your package model and migrations.
[!TIP]
Did you come here from a package? You probably want to read the DATABASE.md file instead.
Keep this package free
Your support allows me to keep this package free, up-to-date and maintainable. Alternatively, you can spread the word!
Requirements
- Laravel 11 or later
Installation
Fire up Composer and require it into your package:
Customizing models
When you create a model in your package, most of the time, your end-developers won't be able to modify it unless they create a repository that manually creates a model. Instead, you can add the HasCustomization trait to your model and let the developer modify the model when is instanced.
[!TIP]
The trait is marked as "internal" to avoid appearing on your IDE.
From there, the end-developer can customize the model by setting a callback to the customize() method, that receives the model instance. For example, you may do this in your bootstrap/app.php through the booted() method.
Custom Migration
You may use the migration() method of the trait to create a hands-off migration that can only be extended. This is a great way to let the developer with an immutable table, but allow them to add columns or change the primary model type for.
The Laragear\MetaModel\CustomMigration class can be created using the create() method. It receives a callback that will be used to create the table. The table name is retrieved automatically from the Model, and it will be automatically dropped when invoking down().
[!TIP]
The callback
$thisis bound to theCustomMigrationinstance, not the model.
Once then, we can create the migration file 0000_00_00_000000_create_cars_table.php. Instead of returning a class that extends the default Laravel migration, we use our model and the migration() method.
Morphs
[!CAUTION]
Morphs are only supported for a single relation. Multiple morphs relations on a single table is highly discouraged.
If your migration requires morph relationships, you will find that end-developers won't always have the same key type in their application to associate with. This problem can be fixed by using the createMorph() or createNullableMorph() method with the Blueprint instance and the name of the morph type.
This will let the end-developer to change the morph type through the morph() method if needed. For example, if he's using ULID morphs for the target models, he may set it in one line:
Default index name
You may also set a custom index name for the morph. It will be used as a default, unless the user overrides it manually.
After Up & Before Down
An end-developer can execute logic after the table is created, and before the table is dropped, using the afterUp() and beforeDown() methods, respectively. This allows the developer to run enhance the table, or avoid failing migrations.
For example, the end-developer can use these methods to create foreign column references, and remove them before dropping the table.
[!IMPORTANT]
The
afterUp()andbeforeDown()adds callbacks to the migration, it doesn't replace them.
Package documentation
If you plan to add this to your package, you may also want to copy-and-paste the DATABASE.md file in your package. This way developers will know how to use your model and migrations. Alternatively, you may also just copy its contents, or link back to this repository.
You may execute this from your project root:
Laravel Octane compatibility
- There are no singletons using a stale application instance.
- There are no singletons using a stale config instance.
- There are no singletons using a stale request instance.
- Trait static properties are only written once by end-developer.
There should be no problems using this package with Laravel Octane.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
License
This specific package version is licensed under the terms of the MIT License, at time of publishing.
Laravel is a Trademark of Taylor Otwell. Copyright © 2011-2025 Laravel LLC.
All versions of meta-model with dependencies
illuminate/database Version 11.*|12.*
illuminate/contracts Version 11.*|12.*
illuminate/container Version 11.*|12.*