Download the PHP package carbon/automigrate without Composer
On this page you can find all versions of the php package carbon/automigrate. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download carbon/automigrate
More information about carbon/automigrate
Files in carbon/automigrate
Package automigrate
Short Description Automatic node migrations for Neos CMS
License GPL-3.0-or-later
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 automigrate
Carbon.AutoMigrate
Sometimes, things change. This package helps you to migrate old installation to up-to-date installations. This help to run migrations after deployments.
Installation
This package is available via packagist. Run composer require carbon/automigrate --no-update in your
site package. After that, run composer update in your root directory.
How to use it
Add your node migrations version numbers to your Settings.yaml:
Configure your stack to run ./flow node:automigrate after ./flow doctrine:migrate. The command will check if the
migrations are available, checks if the migrations has already been applied, and if not, the migrations get's applied.
Options
Run ./flow help node:automigrate to see the options:
Aditional filter migration helper
Filters define which nodes are affected by a migration. They are evaluated before the transformation is executed and work like a condition: only matching nodes are processed.
The most common filters are the built-in ones from the Neos content repository, for example NodeType to restrict a
migration to one node type.
PropertyValue
In addition, this package provides the custom PropertyValue filter to target nodes by a
specific property and value which can be inverted.
PropertyValue searches in the node's serialized properties field for a matching key/value pair. This is useful when
you want to limit a migration to nodes that already contain a certain value. Setting inverted: true reverses the
condition so that only nodes without that property value are processed.
Aditional transformation migration helper
ChangeNumericPropertyValue
Change the numeric value of a given property.
A migration could look like this:
ChangePropertyValue
This is basically the same as the original ChangePropertyValue transformation from Neos.ContentRepository but with the added ability to search and replace in numeric values. * This is useful when you want to change a property value that is a number but you want to change it to a string.
RenamePropertyValues
This can be used to rename one or multiply property values. This is also possible with default yaml, but need many lines, if you have multiple values to change.
A migration could look like this:
RenameNodeTypes
This can be used if you want to rename NodeTypes. This not only change the nodetype in the table
neos_contentrepository_domain_model_nodedata, it also set the siteresourcespackagekey in
neos_neos_domain_model_site if the node type match.
You have to create a PHP file in your package under Migrations/Mysql
The migration will automatically run if you run ./flow doctrine:migrate.
