Schema migrations

[EmanueleMinotto]

I don't see database schema migrations for the production environment, shouldn't migrations be included for the safety of bamboo applications already on production?

Of course to include them should be used the DoctrineMigrationsBundle.

[mmoreram]

@EmanueleMinotto I give you some tips, but I'm agree about evolve this idea...

• Bamboo should be only a base. Is this really important? I mean, given that this project should only be a base, is there any reason why we really need migrations? Give me some light!
• If the response is "OK 200", then, we should use DoctrineMigrationsBundle? Is there any alternative?

Great reminder!

[EmanueleMinotto]

Oh ok, no it isn't really important if bamboo is a dev/test only application, but if someone uses bamboo also in production than schema migrations could become really important:

• doctrine:schema:update could cause bad problems on production, and without migrations a developer could be tempted to do it
• moving from bamboo to something else (even if based on elcodi too) is much more easy with migrations because are only files to move, without them the final developer should be sure that he/she moved everything before generating the new schema (with migrations, after the execution the final developer will have exceptions due to unmapped things)

No, the DoctrineMigrationsBundle isn't the only solution: https://github.com/ziadoz/awesome-php#migrations Anyway I would still recommend it because really well integrated with the sf2 framework.

[mmoreram]

@EmanueleMinotto Great! Then, that's a good idea!

What we could do here is provide the interface of doing that, and why not, turn all our Fixtures into one single migration.

Do you want to take care of it?

Thanks man!

[EmanueleMinotto]

Sure I can :+1:

[mmoreram]

You rock man... :dancers: