You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+119Lines changed: 119 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -378,3 +378,122 @@ Now you’re all set to run the auto-match and reconcile against your purchase o
378
378
*Figure 6: The Auto-Match engine processes your invoice and then confirms a 100% match—every line item and the total perfectly aligned with your Purchase Order.*
379
379
380
380
Instant peace of mind knowing your invoice is exactly what you ordered.
381
+
382
+
383
+
<aid="getting-started"></a>
384
+
## Getting Started
385
+
386
+
Follow these steps to get MatchFlow up and running locally via Docker Compose.
387
+
388
+
---
389
+
390
+
### Prerequisites
391
+
392
+
#### Local Development Tools
393
+
-**Docker Engine** ≥ 20.10
394
+
-**Docker Compose** ≥ 1.29
395
+
- A modern web browser (Chrome, Firefox, Safari, Edge)
396
+
397
+
#### Azure Resources
398
+
Before running MatchFlow, you need to set up these Azure services:
399
+
400
+
-**Azure Blob Storage**
401
+
- Create a storage account
402
+
- Create a container for PDF storage
403
+
- Get the connection string and container name
404
+
405
+
-**Azure Form Recognizer**
406
+
- Create a Form Recognizer resource
407
+
- Get the endpoint URL and API key
408
+
409
+
> **Note:** These Azure resources are required for PDF storage and OCR processing. You'll configure them in the `.env` file during installation.
> **Note:** Populate the `AZUREBLOB__*` and `FORMRECOGNIZER__*` keys in your `.env` file with the Azure resource details you set up in the Prerequisites section.
0 commit comments