Wire admin studio SSR and search infrastructure
This commit is contained in:
@@ -36,10 +36,10 @@ We provide an example Supervisor config at `deploy/supervisor/skinbase-queue.con
|
||||
The example worker listens on the application queues currently used by Skinbase features, including AI and discovery jobs:
|
||||
|
||||
```text
|
||||
forum-security,forum-moderation,vision,recommendations,discovery,mail,default
|
||||
search,forum-security,forum-moderation,vision,recommendations,discovery,mail,default
|
||||
```
|
||||
|
||||
If you split workloads across dedicated workers, make sure any queues configured through `VISION_QUEUE`, `RECOMMENDATIONS_QUEUE`, or `DISCOVERY_QUEUE` are explicitly covered by at least one worker process.
|
||||
If you split workloads across dedicated workers, make sure the Scout/Meilisearch `search` queue and any queues configured through `VISION_QUEUE`, `RECOMMENDATIONS_QUEUE`, or `DISCOVERY_QUEUE` are explicitly covered by at least one worker process.
|
||||
|
||||
To use it on a Debian/Ubuntu server:
|
||||
|
||||
@@ -79,7 +79,7 @@ Adjust `WorkingDirectory` and `User` in the unit to match your deployment.
|
||||
- Start a one-off worker (foreground):
|
||||
|
||||
```bash
|
||||
php artisan queue:work --sleep=3 --tries=3
|
||||
php artisan queue:work --sleep=3 --tries=3 --queue=search,default
|
||||
```
|
||||
|
||||
- Restart all workers gracefully (useful after deployments):
|
||||
@@ -108,6 +108,7 @@ php artisan queue:flush
|
||||
- Ensure `QUEUE_CONNECTION` in `.env` matches the driver you've configured.
|
||||
- If using `database` driver, the `jobs` and `failed_jobs` tables must exist.
|
||||
- The mailable used for contact submissions is queued; if the queue worker is not running mails will accumulate in the queue table (or Redis).
|
||||
- Scout search syncing uses the `search` queue from `config/scout.php`. If workers only consume `default`, `artworks:search-rebuild` will dispatch jobs but new artwork documents will never reach Meilisearch.
|
||||
- AI auto-tagging, embedding generation, vector index repair, and recommendation cache regeneration are all queued. If you move them onto dedicated queues, the shipped example worker commands must be updated to consume those queue names.
|
||||
|
||||
8) AI and discovery queue checklist
|
||||
|
||||
Reference in New Issue
Block a user