continuing issue no. 7 #11

Closed
saggi18dec opened this Issue Nov 18, 2011 · 8 comments

6 participants

@saggi18dec

yes. configuration is done through config.yml files, but there is an option to provide configuration at runtime in the command.
which is not working properly, and the issue is for that.

@paulovitin

I'm having the same problem! =(

@odino
Doctrine member

@saggi18dec can you please provide some more details?

@saggi18dec

If i give configuration file path in the command, and give the migrations directory in that file, its not getting changed.

steps:
created a file : migrations.yml
and typed:
migrations_dir: /path/to/migrations

and given its path in doctrine:migrations:status --configuration="/path/to/migrations.yml"

now, the path given in migrations.yml is not used for generating migration scripts [version*]

The problem is in /DoctrineMigrationsBundle/Command/DoctrineCommand.php

$dir = $container->getParameter('doctrine_migrations.dir_name');
$configuration->setMigrationsDirectory($dir);

The above setting gives problem when we pass the configuration in command line arguments such as:

php console doctrine:migrations:status --configuration=/path/to/configuration.yml

the configuration path is overwritten by above mentioned lines.

@odino
Doctrine member

thx for now ;)

@jrobeson

probably fixed in #95 ?

@jrobeson

@mikeSimonson : can this be closed too then?

@mikeSimonson

@jrobeson I would prefer to close it only when test are made for that issue

@stof
Doctrine member

Closing becuase of doctrine/migrations#219

@stof stof closed this Aug 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment