> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/self-hosting/dotnet-aspire-and-cloud.md).

# .NET Aspire & Cloud

Use Aspire locally and adapt declared resources to adopter-owned cloud infrastructure.

[.NET Aspire](/islamu-event/documentation/readme/contributing/local-development.md) is the repository's development orchestrator and an architectural foundation adopters can adapt for custom cloud infrastructure. Note that ISLAMU Event intentionally does not ship turnkey supported Azure or AWS production cloud templates.

***

## Local Development Orchestration

To run the complete platform orchestrator during local development:

```bash
aspire run --apphost Explore.AppHost/Explore.AppHost.csproj
```

The AppHost declares resources, dependency ordering, service discovery, configuration injection, health checks, and restart relationships (see [Local Development Guide](/islamu-event/documentation/readme/contributing/local-development.md)). Use the Aspire dashboard and resource logs to inspect startup. Ports in Aspire are assigned dynamically; do not assume static Docker Compose port numbers.

***

## Cloud Adaptation Considerations

Aspire can output deployment manifests targeting cloud container environments such as Azure Container Apps (ACA) or AWS ECS when an adopter supplies the hosting infrastructure. The repository does not provide native managed-secret adapters for Azure Key Vault or AWS Secrets Manager; operators must use the approved [Secret Providers (Environment or Infisical)](/islamu-event/documentation/readme/configuration-and-operations/secrets.md).

A production cloud adaptation must explicitly define:

1. **Durable Relational Data**: Primary application database and isolated [Privacy-Erasure Authority](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md).
2. **Object Storage**: [S3-compatible Object Storage](/islamu-event/documentation/readme/integrations-and-ai/storage.md) for media and attachments.
3. **Identity & Authorization**: [Keycloak OIDC Authentication](/islamu-event/documentation/readme/security-and-identity/authentication.md) and [Authorization (Local RBAC or Cerbos)](/islamu-event/documentation/readme/security-and-identity/authorization.md).
4. **Migration Service**: One-shot execution of `Event.MigrationService` before opening web traffic.
5. **Secrets Delivery**: Safe binding via [Secrets Management (Infisical or Environment)](/islamu-event/documentation/readme/configuration-and-operations/secrets.md).
6. **Networking & TLS**: Ingress reverse proxy with trusted forwarder headers (`X-Forwarded-Proto`).
7. **Observability**: Centralized logs, metrics, and health probes (see [Troubleshooting & Health](/islamu-event/documentation/readme/configuration-and-operations/troubleshooting-and-health.md)).
8. **Disaster Recovery**: Automated snapshots and restore rehearsals (see [Backup, Restore & Upgrade](/islamu-event/documentation/readme/configuration-and-operations/backup-restore-upgrade.md)).

***

## Acceptance Criteria

Do not deem a cloud deployment operational merely because containers boot:

* Prove migrations execute cleanly.
* Confirm that Keycloak OIDC redirects back to the Blazor BFF over HTTPS.
* Verify that privacy-erasure replay runs during startup without errors.
* Rehearse a complete restore from database backup.

***

## Related Guides & Next Steps

* [**Local Development with .NET Aspire**](/islamu-event/documentation/readme/contributing/local-development.md) — Step-by-step developer setup instructions.
* [**Docker Compose Runbook**](/islamu-event/documentation/readme/self-hosting/docker-compose.md) — Recommended split container deployment guide.
* [**Deployment Tiers & Sizing**](/islamu-event/documentation/readme/self-hosting/deployment-tiers.md) — Infrastructure sizing matrix for small to large deployments.
* [**Backup, Restore & Upgrade**](/islamu-event/documentation/readme/configuration-and-operations/backup-restore-upgrade.md) — Production backup routines and disaster recovery.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://islamu.gitbook.io/islamu-event/documentation/readme/self-hosting/dotnet-aspire-and-cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.