Hello Pietro,
Thanks for your reply.
I think that using a custom fixture directory is the only solution,
because fixture yaml itself is not environment-aware, isn't it?
Please correct me if I'm wrong.
Thanks and Regards,
JoJo
2010/5/7 Pietrino Atzeni <[email protected]>
> I would like to know the best way to define fixtures by environment.
>>
>> For example, I need some *basic fixtures *for dev/test/prod
>> environment, and some *data fixtures *only for dev and test environment.
>> So when Prod environment, I just load basic fixtures.
>>
>> I think that this could be done by defined a custom fixture
>> directory, and launch the data-load with option --*dir*, but is this
>> only way to do this or there is better solution?
>>
>> Any suggestion is welcomed.
>>
>> Thanks and Regards,
>>
>> JoJo
>>
> Yes, you can use that option --dir, or you can define a task that makes all
> your deployment to the test/prod environments: rsync, set permissions,
> migrate db, load fixtures.
>
> Hope this helps,
> Pietro
>
>
> --
> If you want to report a vulnerability issue on symfony, please send it to
> security at symfony-project.com
>
> You received this message because you are subscribed to the Google
> Groups "symfony users" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<symfony-users%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/symfony-users?hl=en
>
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
