Skip to content

Conversation

@Vemarthula-Microsoft
Copy link
Contributor

Purpose

This pull request introduces a comprehensive local development guide for the project. The new LocalSetupGuide.md file provides step-by-step instructions for setting up the development environment, deploying resources, running and debugging the solution locally, and troubleshooting common issues. This documentation is intended to streamline onboarding and improve the developer experience.

The most important changes are:

New developer documentation:

  • Added a detailed docs/LocalSetupGuide.md file covering prerequisites, environment setup, deployment steps, and component-specific instructions for both backend and frontend development.
  • Included sections for debugging, troubleshooting common issues (such as port conflicts, authentication, and CORS), and links to further resources and support.

Environment and deployment guidance:

  • Provided instructions for using VS Code Dev Containers, setting up .env files, and configuring Azure resources and permissions.
  • Documented how to run and debug each service (API, processor, and web frontend) locally, including sample launch.json configurations for VS Code.

Troubleshooting and support:

  • Added a troubleshooting section with solutions for common development environment problems and guidance on enabling debug logging.

Does this introduce a breaking change?

  • Yes
  • No

Golden Path Validation

  • I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

  • I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

  • ...

Other Information

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR introduces comprehensive local development documentation for the Content Processing Solution Accelerator. It provides step-by-step instructions for setting up and running the solution locally, including prerequisites, environment configuration, debugging, and troubleshooting.

Key changes:

  • Added detailed setup instructions covering prerequisites, dev container usage, and Azure resource deployment
  • Documented configuration steps for all three components (API, Processor, and Web frontend) with platform-specific commands
  • Included comprehensive troubleshooting section addressing common development environment issues

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

```

**Troubleshooting startup:**
- If you get "Forbidden" errors from App Configuration or Cosmos DB, ensure your Azure role assignments have propagated (wait 5-10 minutes after creating them)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Give the list of roles that developer needs to have as prerequisite

--scope "/subscriptions/$SUBSCRIPTION_ID/resourceGroups/<resource-group>/providers/Microsoft.DocumentDB/databaseAccounts/<cosmos-name>"

# 3. Storage Queue Data Contributor
az role assignment create \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We upload blob as well, so user might need to have Blob contributor role as well, cross check all roles that are assigned to API & Processor Container App and add missing roles

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
```

### 3.3. Install Dependencies
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Content processing uses uv sync as package manager

APP_CONFIG_ENDPOINT=https://<your-appconfig-name>.azconfig.io

# Cosmos DB endpoint from your Azure deployment
AZURE_COSMOS_ENDPOINT=https://<your-cosmos-name>.documents.azure.com:443/
Copy link
Contributor

@Prajwal-Microsoft Prajwal-Microsoft Dec 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these keys AZURE_COSMOS_ENDPOINT & AZURE_COSMOS_DATABASE really required to be added in .env as they are read from App Config, check if these keys are present in App Config.

│ │ ├── .venv/ ← Virtual environment
│ │ └── src/
│ │ ├── main.py ← Processor entry point
│ │ └── .env.dev ← Processor config file
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

.env.dev seems to be a sample .env file, which we no need to represent here.


### 4.4. Configure Environment Variables

Create a `.env.dev` file (note the `.dev` suffix) in the `src/ContentProcessor/src/` directory:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be .env file utself, .env.dev does not load automatically

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rename the file as per the standard

…mprehensive instructions for setting up the Content Processing Solution Accelerator for local development on Windows and Linux.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants