Skip to content

Commit 0fe224b

Browse files
Update Cloud screenshots (#3367)
1 parent 61c3080 commit 0fe224b

File tree

5 files changed

+16
-7
lines changed

5 files changed

+16
-7
lines changed
-9.36 KB
Loading
25.5 KB
Loading

learn/async/working_with_tasks.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,17 +48,17 @@ Meilisearch processes tasks in the order they were added to the queue. You can c
4848

4949
### Monitoring task status in the Meilisearch Cloud interface
5050

51-
Log into your [Meilisearch Cloud](https://meilisearch.com/cloud?utm_campaign=oss&utm_source=docs&utm_medium=tasks-tutorial) account and navigate to your project. Click the "Tasks" link in the project menu:
51+
Log into your [Meilisearch Cloud](https://meilisearch.com/cloud) account and navigate to your project. Click the "Tasks" link in the project menu:
5252

5353
![Meilisearch Cloud menu with "Tasks" highlighted](/assets/images/cloud-tasks-tutorial/01-tasks-menu.png)
5454

55-
This will lead you to the task overview. Look for your request's `taskUid` in the "Uid" column:
55+
This will lead you to the task overview, which shows a list of all batches enqueued, processing, and completed in your project:
5656

5757
![A table listing multiple Meilisearch Cloud tasks](/assets/images/cloud-tasks-tutorial/02-tasks-table.png)
5858

59-
When the task `status` changes to `succeeded`, Meilisearch has finished processing your request.
59+
All Meilisearch tasks are processed in batches. When the batch containing your task changes its `status` to `succeeded`, Meilisearch has finished processing your request.
6060

61-
If the task `status` changes to `failed`, Meilisearch was not able to fulfill your request. Check the task object's `error` field for more information.
61+
If the `status` changes to `failed`, Meilisearch was not able to fulfill your request. Check the object's `error` field for more information.
6262

6363
### Monitoring task status with the Meilisearch API
6464

learn/security/basic_security.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,10 @@ The master key is the first and most important step to secure your Meilisearch p
1818

1919
Meilisearch Cloud automatically generates a master key for each project. This means Meilisearch Cloud projects are secure by default.
2020

21-
You can view your master key by visiting your project overview:
21+
You can view your master key by visiting your project settings, then clicking "API Keys" on the sidebar:
2222

2323
<Frame>
24-
<img src="/assets/images/security/01-master-api-keys.png" alt="An interface element named 'API keys' showing three obscured keys: 'Master key', 'Default Search API Key', and 'Default Admin API Key'" />
24+
<img src="/assets/images/security/01-master-api-keys.png" alt="An interface element named 'API keys' showing obscured security keys including: 'Master key', 'Default Search API Key', and 'Default Admin API Key'" />
2525
</Frame>
2626

2727
### Creating the master key in a self-hosted instance
@@ -87,7 +87,7 @@ When your project is protected, Meilisearch automatically generates two API keys
8787

8888
### Obtaining API keys in Meilisearch Cloud
8989

90-
Find your API keys in the same section where you previously located the master key:
90+
Find your API keys by visiting your project settings, then clicking "API Keys" on the sidebar:
9191

9292
<Frame>
9393
<img src="/assets/images/security/01-master-api-keys.png" alt="An interface element named 'API keys' showing three obscured keys: 'Master key', 'Default Search API Key', and 'Default Admin API Key'" />
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
<CodeGroup>
2+
3+
```bash cURL
4+
curl \
5+
-X POST 'MEILISEARCH_URL/indexes/restaurants/search' \
6+
-H 'Content-type:application/json' \
7+
--data-binary '{ "filter": "_geoPolygon([45.494181, 9.214024], [45.449484, 9.179175], [45.449486, 9.179177])" }'
8+
```
9+
</CodeGroup>

0 commit comments

Comments
 (0)