cCoder.Packaging 2026.9.12.1247

cCoder.Packaging

View the latest code coverage report

Local configuration

The Web app binds the complete configuration root to Packaging.Web.Models.AppConfiguration. Its composition root registers CoreData, Packaging, SecurityData, Security, and Eventing side by side.

Persistence belongs to the Data domains. PackagingConfiguration contains only Packaging behavior and package-source settings; CoreData owns the database connection, Data registration, and migrations. Likewise, SecurityData owns the Security database and Security contains authentication behavior. Leave secret values empty and define these user- or machine-level environment variables:

• CoreData__ConnectionString
• SecurityData__ConnectionString
• Security__DecryptionKey
• Eventing__ServiceBus__ConnectionString when Service Bus eventing is selected

CoreData__AdminConnectionString and SecurityData__AdminConnectionString are optional migration-only overrides. If an admin connection is configured, startup migrations use it and normal runtime operations continue to use the regular connection. If it is omitted, migrations use the regular connection.

Library consumers register persistence and behavior explicitly at their own composition root: call AddData before AddPackaging or AddPackagingWeb; Web hosts also call AddSecurityData before AddSecurityWeb. An application that consumes cCoder.Core should use Core's composite API instead; Core deliberately composes its configured child domains recursively.

Restart Visual Studio after changing environment variables and press F5. No conversion, .env file, or startup script is required.

cCoder.Packaging contains the Packaging domain for the cCoder platform.

Functionality

Packaging provides a small domain for grouping portable data into packages and package items. It is intended to support migration-style movement of data between cCoder systems, while keeping the package metadata and package item payloads queryable through the normal API stack.

Consumers get:

• Package CRUD through OData.
• Package item CRUD within the context of a package.
• Export orchestration for known cCoder domains such as content, documents, workflow, scheduling, and app security.
• Import orchestration hooks that raise package import events.
• A simple authenticated Web app for manually testing package and package item CRUD.

Full migration scenarios need a deliberate source and target environment, so this repository does not introduce a synthetic two-database integration harness. The Web UI and acceptance tests provide the baseline proof that the package API surface starts and responds correctly.

Contents

• src/cCoder.Packaging The main library package published to NuGet.
• src/cCoder.Packaging.Tests Unit tests for the domain.
• src/Apps/Packaging.Web A simple Web app hosting the Packaging API and manual testing UI.
• src/Apps/Packaging.Web.AcceptanceTests HTTP acceptance tests for the Packaging Web app.

Configuration

Packaging.Web uses the normal application configuration pipeline:

• appsettings.json
• appsettings.{Environment}.json
• environment variables

The committed settings map directly to the CoreData, Eventing, Packaging, SecurityData, and Security configuration objects. Secrets use the matching environment variables listed above.

The local test UI is available at /tools/index.html, and /Health returns a fixed OK response for basic health checks.

Build

dotnet build src/cCoder.Packaging.slnx -v minimal

Test

dotnet test src/cCoder.Packaging.slnx -v minimal --no-build

Run The Web App

dotnet run --project src/Apps/Packaging.Web/Packaging.Web.csproj --launch-profile https

Then open:

• https://localhost:7173/tools/index.html
• https://localhost:7173/swagger
• https://localhost:7173/Health

Package

The NuGet package produced by this repository is:

• cCoder.Packaging

Publishing

GitHub Actions is configured to publish the main package using NuGet trusted publishing.

Before the first publish, configure a trusted publishing policy on nuget.org for:

• Repository owner: ccoder-co-uk
• Repository: cCoder.Packaging
• Workflow file: publish.yml

The workflow also expects a NUGET_USER repository secret containing the nuget.org profile name used during trusted publishing login.