How murcex/m-core works
Project type and purpose
• This is a monorepo hosting multiple .NET solutions (Configurator, Crane, Implements, KirokuG2, PlyQor, Sensor), each exposing C# Azure Functions (Function apps) or CLI tools (Crane) backed by SQL Server scripts.
• Purpose: provide a suite of domain-specific microservices and libraries for configuration, auditing, data ingestion/processing (KirokuG2, PlyQor, Sensor) plus a standalone SQL-deployment CLI (Crane) and shared “Implements” modules (serialization, encryption, logging).
File structure
• Top-level folders = distinct products or modules.
• <Product>/…-database contains SQL schema/procs.
• <Product>/*-solution contains one or more Azure Function projects (Function.Injektr, Function.Processor, Function.Service, Function.Storage, Function.Scanner, etc.), each with host.json and triggers in Functions/.
• Within solutions there’s an Internal.Engine library (business logic + data-access components) and a client SDK project (Module.Client).
• Implements holds reusable modules (configuration, conversion, encryption, logging).
• Crane is a console-app solution with a core engine and SQL deployment tasks.
• Modules/…nupkg holds built NuGet packages.
Key insights from README
• Minimal direct insight; directs to broader “M Apps” documentation.
• Confirms this is part of a larger product family (“M-Apps”).