Skip to content

incursa/platform

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

210 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Incursa Platform

Incursa.Platform is a public .NET monorepo for reusable platform capabilities, hosting adapters, and vendor integrations. The repository is organized around two package layers:

  • Layer 2 capability packages in src/Incursa.Platform.*
  • Layer 1 vendor integration packages in src/Incursa.Integrations.*

The goal is to keep provider-neutral contracts and domain models clean, small, and reusable, while still shipping first-class vendor-specific adapters for the systems those capabilities need to talk to.

Start Here

Repository Layout

  • src/ contains public packages that are intended to ship from this repository.
  • tests/ contains automated tests and sample or smoke-host projects.
  • docs/ contains architecture notes, quality rules, runbooks, and reference material.
  • eng/ contains packaging, affected-project, and release support scripts.
  • tools/ contains shipped build/runtime helpers and test-support utilities.
  • incubating/ is a staging area reserved for code that is not yet ready for the public source tree.

Layer 2 Capabilities

These packages define the reusable, provider-neutral capability surface of the platform.

Core and foundation

Business and integration capabilities

Hosting and provider-neutral adapters

Storage and persistence adapters

Layer 1 Integrations

These packages are vendor-specific adapters. They are public, packable packages, but they are intentionally scoped to a particular provider.

WorkOS

Cloudflare

Electronic notary

Storage providers

How To Navigate The Repo

  • Start with a layer 2 package if you are trying to understand the platform’s public domain model or capability boundary.
  • Start with a layer 1 integration package if you already know the provider you need and want the vendor-specific adapter.
  • Use the architecture docs before moving code between package families; those documents define what belongs in capability packages versus provider packages.

Packaging And Release Model

Local Validation

dotnet restore Incursa.Platform.CI.slnx
dotnet tool restore
dotnet build Incursa.Platform.CI.slnx -c Release
dotnet test Incursa.Platform.CI.slnx -c Release
pwsh -File eng/Generate-PackageCatalog.ps1
pwsh -File eng/Pack-PublicPackages.ps1 -Configuration Release -OutputPath ./nupkgs

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors