I would like to pose this as a question, since I am not sure if my use case makes sense or not.

Background
I am migrating a Laravel 5.1 + algolia/algoliasearch-laravel application to Laravel 5.5 + Laravel Scout. This application is worked on by multiple developers, and the application is deployed on DTAP-style environments. In the current setup all index settings are properties of respective models. The $perEnvironment setting is used as well. Using this we have achieved a index per environment, with each developer having his own index (because he/she names the environment "jdoe_dev").

Current situation
The model contains the index settings. On a deploy (on any of the DTAP environments), the settings as they are at that moment in git history are pushed to Algolia with a custom Artisan command that hooks into the algoliasearch-laravel API.

Laravel Scout Settings
Since we're using multiple indexes in the same Algolia app, i.e. for test, acceptance and production, I would have to commit the setting-json files in triple. But I would have to manually update those files, since on my dev environment, the backup command would create another set of json files. Also, if at some point the environment name would change (which we did in the past, when we replaced "staging" with "test" and "acceptance"), it would require some more changes to the setting files as well.

I see no benefit to this. The way the plugin works, it would always only use one set of json files.

Suggested change
I think it would be possible to cater to my use case (which I don't think is uncommon/illogical, but correct me if I'm wrong... 😅) whilst keeping the default behavior the same. Instead of directly using the index name to concat the filename, use a mediating function in between, something like AlgoliaCommand::getBaseFileName($indexName). By default this would then just return $indexName, but if set, an alternative callback could be executed to get the base file name to be used.

If you want, I could try and make a PR for this?

Can you make the latest commit an available release?

I'm using Scout Extended package for Laravel, which requires algoliasearch-client-php version 2+. So can't install this package with extended scout.

Thanks in advance!

It would be nice to add a changelog 🚀

I cannot set "forwardToReplicas":true in my json settings and there is no way to set it from the dashboard. Is there a way to achieve this?

With version 2.0.0 this package now has the capability to save the settings-files without the prefix defined by the env value SCOUT_PREFIX and used in Laravel with config('scout.prefix').

This change was, I think, initiated by my earlier issue #14 . It is however still not enough to support my use case. This mostly relates to how replicas and primaries are defined in the settings.

Example background:

• Table is called "posts"
• Scout prefix is "test_"
• Two indices; primary "test_posts" and replica "test_posts_newest"

When the backup command is run, without prefix, files named "posts.json" and "posts_newest.json" will be created. Which is great, since their not tied to a specific environment. But the JSON in those files have properties that are environment specific, like "replicas": ["test_posts_newest"] and "primary": "test_posts".

I am embarrassed that this slipped my attention when checking my PR and making the testcases. I am creating this issue mostly to:

• Check again my use case is valid
• Discuss the direction of implementation of a PR (which I would be happy to make)

My suggestion would be:

• On backup manipulate settings to remove the prefix from both the primary and replicas, similar to how it is removed from the filenames.
• On push manipulate settings to add back the prefix. This is actually a bit tricky to do in a fail-proof manner, since the searchableAs() methodology of Scout offers a lot of freedom in naming an index. Perhaps the indexname as know to Algolia should be kept on the repository too, just like the usePrefix-setting.

It seems algolia's packages aren't fully updated regarding laravel/scout 4.0

Description

The documentation on Algolia.com for laravel-scout-settings contains incorrect examples that will fail, originally corrected in PR #7

Steps To Reproduce

Visit https://www.algolia.com/doc/api-client/laravel/managing-settings/?language=laravel#how-to-use

Without the use of quotes around the classname, the console command is striping characters from $this->argument('model') (App\ClassName becomes AppClassName).

Possible Fixes

• As per @ChrisThompsonTLDR, update documentation to include quotes around the class name: "App\ClassName"
• Or change documentation to escape backslash in command: App\\ClassName

It seems this package is not supporting Laravel/Scout 5.0.+. I'd appreciate it if anyone can help me with this.

Hello!

We have a custom trait that uses the Laravel Scout classes but from the models, we use our trait (which is basically a wrapper).

We are getting the error while running the artisan commands "... does not use the [Laravel\Scout\Searchable] trait". (But we do in our custom wrapper.

We commented the lines of code that do the check on the BackupCommand.php and PushCommand.php and the rest works perfect.

So we were thinking that maybe you could have an extra setting like you do with the folder customization, to allow to skip the check of "isClassSearchable". Maybe like: ALGOLIA_SETTINGS_SKIP_CHECK=true.

If not we can do a fork and maintain a parallel package... We can do a PR if you like!

Thanks!