2025-02-10までの原文変更点反映。

Author: HiroKws

Diff for: original-en/mail.md

@@ -59,7 +59,11 @@ To use the Mailgun driver, install Symfony's Mailgun Mailer transport via Compos
 composer require symfony/mailgun-mailer symfony/http-client
 ```
 
-Next, set the `default` option in your application's `config/mail.php` configuration file to `mailgun` and add the following configuration array to your array of `mailers`:
+Next, you will need to make two changes in your application's `config/mail.php` configuration file. First, set your default mailer to `mailgun`:
+
+    'default' => env('MAIL_MAILER', 'mailgun'),
+
+Second, add the following configuration array to your array of `mailers`:
 
     'mailgun' => [
         'transport' => 'mailgun',

Diff for: original-en/migrations.md

@@ -416,7 +416,6 @@ The schema builder blueprint offers a variety of methods that correspond to the
 [string](#column-method-string)
 [text](#column-method-text)
 [tinyText](#column-method-tinyText)
-[longText](#column-method-longText)
 
 </div>
 

Diff for: original-en/scout.md

@@ -123,7 +123,7 @@ For more information regarding Meilisearch, please consult the [Meilisearch docu
 
 In addition, you should ensure that you install a version of `meilisearch/meilisearch-php` that is compatible with your Meilisearch binary version by reviewing [Meilisearch's documentation regarding binary compatibility](https://github.com/meilisearch/meilisearch-php#-compatibility-with-meilisearch).
 
-> [!WARNING]  
+> [!WARNING]
 > When upgrading Scout on an application that utilizes Meilisearch, you should always [review any additional breaking changes](https://github.com/meilisearch/Meilisearch/releases) to the Meilisearch service itself.
 
 <a name="typesense"></a>
@@ -281,6 +281,49 @@ Some search engines such as Meilisearch will only perform filter operations (`>`
         ];
     }
 
+<a name="configuring-indexes-for-algolia"></a>
+#### Configuring Index Settings (Algolia)
+
+Sometimes you may want to configure additional settings on your Algolia indexes. While you can manage these settings via the Algolia UI, it is sometimes more efficient to manage the desired state of your index configuration directly from your application's `config/scout.php` configuration file.
+
+This approach allows you to deploy these settings through your application's automated deployment pipeline, avoiding manual configuration and ensuring consistency across multiple environments. You may configure filterable attributes, ranking, faceting, or [any other supported settings](https://www.algolia.com/doc/rest-api/search/#tag/Indices/operation/setSettings).
+
+To get started, add settings for each index in your application's `config/scout.php` configuration file:
+
+```php
+use App\Models\User;
+use App\Models\Flight;
+
+'algolia' => [
+    'id' => env('ALGOLIA_APP_ID', ''),
+    'secret' => env('ALGOLIA_SECRET', ''),
+    'index-settings' => [
+        User::class => [
+            'searchableAttributes' => ['id', 'name', 'email'],
+            'attributesForFaceting'=> ['filterOnly(email)'],
+            // Other settings fields...
+        ],
+        Flight::class => [
+            'searchableAttributes'=> ['id', 'destination'],
+        ],
+    ],
+],
+```
+
+If the model underlying a given index is soft deletable and is included in the `index-settings` array, Scout will automatically include support for faceting on soft deleted models on that index. If you have no other faceting attributes to define for a soft deletable model index, you may simply add an empty entry to the `index-settings` array for that model:
+
+```php
+'index-settings' => [
+    Flight::class => []
+],
+```
+
+After configuring your application's index settings, you must invoke the `scout:sync-index-settings` Artisan command. This command will inform Algolia of your currently configured index settings. For convenience, you may wish to make this command part of your deployment process:
+
+```shell
+php artisan scout:sync-index-settings
+```
+
 <a name="configuring-filterable-data-for-meilisearch"></a>
 #### Configuring Filterable Data and Index Settings (Meilisearch)
 
@@ -400,7 +443,7 @@ Enabling this feature will also pass the request's IP address and your authentic
 <a name="database-engine"></a>
 ### Database Engine
 
-> [!WARNING]  
+> [!WARNING]
 > The database engine currently supports MySQL and PostgreSQL.
 
 If your application interacts with small to medium sized databases or has a light workload, you may find it more convenient to get started with Scout's "database" engine. The database engine will use "where like" clauses and full text indexes when filtering results from your existing database to determine the applicable search results for your query.
@@ -441,7 +484,7 @@ public function toSearchableArray(): array
 }
 ```
 
-> [!WARNING]  
+> [!WARNING]
 > Before specifying that a column should use full text query constraints, ensure that the column has been assigned a [full text index](/docs/{{version}}/migrations#available-index-types).
 
 <a name="collection-engine"></a>
@@ -496,7 +539,7 @@ If you would like to modify the query that is used to retrieve all of your model
         return $query->with('author');
     }
 
-> [!WARNING]  
+> [!WARNING]
 > The `makeAllSearchableUsing` method may not be applicable when using a queue to batch import models. Relationships are [not restored](/docs/{{version}}/queues#handling-relationships) when model collections are processed by jobs.
 
 <a name="adding-records"></a>
@@ -529,7 +572,7 @@ Or, if you already have a collection of Eloquent models in memory, you may call
 
     $orders->searchable();
 
-> [!NOTE]  
+> [!NOTE]
 > The `searchable` method can be considered an "upsert" operation. In other words, if the model record is already in your index, it will be updated. If it does not exist in the search index, it will be added to the index.
 
 <a name="updating-records"></a>
@@ -625,7 +668,7 @@ Sometimes you may need to only make a model searchable under certain conditions.
 
 The `shouldBeSearchable` method is only applied when manipulating models through the `save` and `create` methods, queries, or relationships. Directly making models or collections searchable using the `searchable` method will override the result of the `shouldBeSearchable` method.
 
-> [!WARNING]  
+> [!WARNING]
 > The `shouldBeSearchable` method is not applicable when using Scout's "database" engine, as all searchable data is always stored in the database. To achieve similar behavior when using the database engine, you should use [where clauses](#where-clauses) instead.
 
 <a name="searching"></a>
@@ -682,7 +725,7 @@ The `whereNotIn` method verifies that the given column's value is not contained
 
 Since a search index is not a relational database, more advanced "where" clauses are not currently supported.
 
-> [!WARNING]  
+> [!WARNING]
 > If your application is using Meilisearch, you must configure your application's [filterable attributes](#configuring-filterable-data-for-meilisearch) before utilizing Scout's "where" clauses.
 
 <a name="pagination"></a>
@@ -719,7 +762,7 @@ Of course, if you would like to retrieve the pagination results as JSON, you may
         return Order::search($request->input('query'))->paginate(15);
     });
 
-> [!WARNING]  
+> [!WARNING]
 > Since search engines are not aware of your Eloquent model's global scope definitions, you should not utilize global scopes in applications that utilize Scout pagination. Or, you should recreate the global scope's constraints when searching via Scout.
 
 <a name="soft-deleting"></a>
@@ -739,7 +782,7 @@ When this configuration option is `true`, Scout will not remove soft deleted mod
     // Only include trashed records when retrieving results...
     $orders = Order::search('Star Trek')->onlyTrashed()->get();
 
-> [!NOTE]  
+> [!NOTE]
 > When a soft deleted model is permanently deleted using `forceDelete`, Scout will remove it from the search index automatically.
 
 <a name="customizing-engine-searches"></a>

Diff for: translation-ja/mail.md

@@ -59,7 +59,11 @@ Mailgunドライバを使用する場合は、Composerで、SymfonyのMailgun Ma
 composer require symfony/mailgun-mailer symfony/http-client
 ```
 
-次に、アプリケーションの`config/mail.php`設定ファイルの`default`オプションを`mailgun`へ設定し、次の設定配列を`mailers`設定配列へ追加します：
+次に、アプリケーションの`config/mail.php`設定ファイルへ、２つの変更を加える必要があります。まず、デフォルトのメーラーを`mailgun`に設定します。
+
+    'default' => env('MAIL_MAILER', 'mailgun'),
+
+それから、以下の設定配列を`mailers`配列へ追加します。
 
     'mailgun' => [
         'transport' => 'mailgun',

Diff for: translation-ja/migrations.md

@@ -416,7 +416,6 @@ php artisan migrate:fresh --database=admin
 [string](#column-method-string)
 [text](#column-method-text)
 [tinyText](#column-method-tinyText)
-[longText](#column-method-longText)
 
 </div>
 

Diff for: translation-ja/scout.md

@@ -281,6 +281,49 @@ Meilisearchなどの検索エンジンでは、正しい型のデータに対し
         ];
     }
 
+<a name="configuring-indexes-for-algolia"></a>
+#### インデックス構成の設定（Algolia）
+
+Algoliaのインデックスへ設定を追加したい場合もあるでしょう。これらの設定はAlgoliaのUIから管理できますが、アプリケーションの`config/scout.php`設定ファイルで直接インデックス設定の望ましい状態を管理する方が効率的な場合もあります。
+
+このアプローチにより、アプリケーションの自動デプロイパイプラインを通じて、これらの設定をデプロイできるようになります。手作業による設定を回避し、複数の環境間での一貫性を確保できます。フィルタリング可能な属性、ランキング、ファセット、もしくは[サポート済みのその他の設定](https://www.algolia.com/doc/rest-api/search/#tag/Indices/operation/setSettings)を設定可能です。
+
+これを始めるには、アプリケーションの`config/scout.php`設定ファイルへ各インデックスの設定を追加します。
+
+```php
+use App\Models\User;
+use App\Models\Flight;
+
+'algolia' => [
+    'id' => env('ALGOLIA_APP_ID', ''),
+    'secret' => env('ALGOLIA_SECRET', ''),
+    'index-settings' => [
+        User::class => [
+            'searchableAttributes' => ['id', 'name', 'email'],
+            'attributesForFaceting'=> ['filterOnly(email)'],
+            // その他の設定項目…
+        ],
+        Flight::class => [
+            'searchableAttributes'=> ['id', 'destination'],
+        ],
+    ],
+],
+```
+
+指定するインデックスの元となるモデルが、ソフトデリート可能で、`index-settings`配列に含まれている場合、Scoutはそのインデックスのソフトデリート済みモデルに対するファセットを自動的にサポートします。ソフトデリート可能なモデルインデックスに対し定義するファセット属性が他にない場合は、そのモデルに対して`index-settings`配列に空のエントリを追加するだけです。
+
+```php
+'index-settings' => [
+    Flight::class => []
+],
+```
+
+アプリケーションのインデックス設定を行った後は、`scout:sync-index-settings` Artisanコマンドを起動する必要があります。このコマンドは現在設定しているインデックス設定をAlgoliaへ通知します。このコマンドをデプロイプロセスの一部とすると便利でしょう。
+
+```shell
+php artisan scout:sync-index-settings
+```
+
 <a name="configuring-filterable-data-for-meilisearch"></a>
 #### Filterableデータとインデックス（Meilisearch）の設定