[Neos] Pupose Of The Migration Folder

Chris Tete tetechris20 at yahoo.com
Mon Aug 11 12:53:15 CEST 2014

Hi Dominique,
                         Thanks for reply to my question fast, I like to know if I have to include a migration folder when integrating a standlone package as a backend module in neos?

Krys Nuvad

On Monday, August 11, 2014 3:43 AM, Dominique Feyer <dfeyer at ttree.ch> wrote:

Hi Krys,

In Flow or Neos you can have different migration:

1. Doctrine (database related)
2. TYPO3CR (Content Repository related)
3. Code (PHP related)

To be short migration can automatically update your database based on change in the database or code.

For Doctrine you can use the CLI utility. For TYPO3CR and code migration, it’s a manual operation to create migration script.

Migration are really useful when you deploy your application, because the database or CR structure migration can be applied automatically (same thing if your work with multiple developer). Doctrine or TYPO3CR migration are related to your data structure.

Check the document about Doctrine migration here:

Code migration is a bit different. In the case you open source a package that contain a nice utility, and you decide the change the public API, by per ex. renaming some function. You can write a code migration script that will help your user to update their own code to match your new API.

Hope that clarify the use case of the difference migrations.

ttree sàrl 
Dominique Feyer 
Rue du Valentin 34 et demi
CH - 1004 Lausanne
+41 21  312 36 35 
 dfeyer at ttree.ch  
ttree.ch - @ttreeagency - plan d’accès 

Le 11 août 2014 à 12:31:30, Chris Tete (tetechris20 at yahoo.com) a écrit:
Hello Everyone, 
>                            Please I would like someone to explain to me how the files in the migration folder of the media browser package works or better still what it is use for. 
>Just need an overview of how it works 
>Krys Nuvad 
>Neos mailing list 
>Neos at lists.typo3.org 

More information about the Neos mailing list