Open guerinj opened 5 years ago
Hi,
We have recently upgraded to scout-extended from v1. Previously we used to store the indices config in our code base.
But with the new scout:sync behaviour, the configuration files contains the prefix.
On my dev configuration I prefix all indices with dev_ so all configuration files are scout-dev-foo.php
dev_
scout-dev-foo.php
But to update the production configuration upon deployment, I need a scout-prod-foo.php file
scout-prod-foo.php
What I'd like would be to have a scout-foo.php config files and the scout:sync method would add the prefix upon synchronization.
scout-foo.php
scout:sync
Am i missing an easy way to fix this without having to rename the files when deploying ?
Not today - I am sorry.
Would you like to tackle this? How about this pull request? https://github.com/algolia/scout-extended/pull/135/files
Hi,
We have recently upgraded to scout-extended from v1. Previously we used to store the indices config in our code base.
But with the new scout:sync behaviour, the configuration files contains the prefix.
On my dev configuration I prefix all indices with
dev_
so all configuration files arescout-dev-foo.php
But to update the production configuration upon deployment, I need a
scout-prod-foo.php
fileWhat I'd like would be to have a
scout-foo.php
config files and thescout:sync
method would add the prefix upon synchronization.Am i missing an easy way to fix this without having to rename the files when deploying ?