InstallHub Integration
MarketHub handles discovery, reputation, and community. InstallHub handles the technical export and import pipeline. Together they form the complete BizFirstGO package ecosystem — separate systems with a clean handoff point.
Division of Responsibility
| Concern | MarketHub | InstallHub |
|---|---|---|
| Package discovery and search | Yes | No |
| Package detail pages, reviews, ratings | Yes | No |
| Publisher profiles and reputation | Yes | No |
| Community forums and Q&A | Yes | No |
| Admin governance and audit | Yes | No |
| Package export (artifact bundling) | No | Yes |
| Package import (artifact deployment) | No | Yes |
| Dependency resolution during import | No | Yes |
| Conflict detection (name collisions) | No | Yes |
| Tenant-side install tracking (count back to MarketHub) | Receives count | Reports count |
The Install Flow
When a user clicks Install on a MarketHub package detail page, control transfers to the InstallHub import pipeline in the user's tenant. The handoff carries the package identifier and version so InstallHub can fetch the package manifest directly.
User Clicks Install on MarketHub
MarketHub redirects to the InstallHub import entry point with the package ID and selected version in the URL parameters.
InstallHub Fetches Package Manifest
InstallHub retrieves the package manifest from MarketHub's package API. The manifest lists all artifacts and declared dependencies.
Dependency Resolution
InstallHub walks the dependency graph. Packages already installed in the tenant at a compatible version are reused; missing dependencies are queued for installation.
Conflict Detection
InstallHub checks for naming conflicts with existing artifacts. If conflicts exist, the user sees a conflict resolution screen before proceeding.
Preview and Confirm
The user sees a preview: what will be created, what will be updated, and what dependencies will be installed. They confirm to proceed.
Artifacts Deployed
InstallHub deploys all artifacts into the tenant. On success, it reports the install event back to MarketHub — incrementing the install counter for the package.
Install Count Reporting
When InstallHub successfully completes an install, it calls back to the MarketHub API to record the install event. This is how the install counter on package cards stays current. The callback includes the package ID, version installed, and tenant identifier (anonymized — only the count is exposed publicly).
Install counts drive publisher reputation point accumulation: each unique tenant install awards the publisher +1 reputation point.
Anonymous users can browse MarketHub freely. The Install button becomes active only for authenticated users. Clicking Install while anonymous redirects to the BizFirstGO login page first.