When using Algolia with Scout Extended, what is the purpose of having the index settings in both a config file and in Algolia? I know that you can sync settings from local to remote and vise-versa. I'm just wondering why not only configure those settings Algolia-side and not worry with keeping them in sync?
Everyone on your team can use their own Algolia keys for local development. And your production app will have it's own keys as well. This way, you can seed Algolia with dummy data, play around with settings , etc... and your live app won't be affected. Only your saved changed to the Algolia configuration files will be synced to your production app.
You can do this automatically in your deploy script:
When using Algolia with Scout Extended, what is the purpose of having the index settings in both a config file and in Algolia? I know that you can sync settings from local to remote and vise-versa. I'm just wondering why not only configure those settings Algolia-side and not worry with keeping them in sync?
https://speedtest.vet/
