Signed distribution endpoint

Secure runtime delivery. Built for every node.

Fetch verified DC Core runtime artifacts, install them as managed services, and apply controlled updates from one native downloader.

  • Signed checksums
  • Transactional updates
  • Service-aware installs
DC CORE / DOWNLOADER READY

CHOOSE YOUR OPERATING SYSTEM

Install for Linux

01 Download and allow execution

$ curl -fsSL https://cud.dccore.io/dcc_downloader_linux -o dcc-downloader
$ chmod +x dcc-downloader

02 Download a named artifact

$ ./dcc-downloader <artifact_name>

The downloader verifies the signed checksum and SHA-256 digest before it extracts or installs anything.

CONTROLLED DELIVERY PATH

Immutable artifacts Fixed-size chunks Signature verification Atomic activation

USE THE DOWNLOADER

One binary.
Three operating modes.

Use a one-time download for manual operations, or let the downloader install and supervise the artifact as an operating-system service. Administrator or root privileges are required for managed service operations.

Use the exact identifier supplied by your deployment configuration or administrator.

Using placeholder
01 / ONE-TIME

Download and extract

Fetch a named artifact into the current directory without installing a service.

./dcc-downloader <artifact_name>
Verified before extraction
02 / MANAGED

Install as a service

Run continuously as a managed background service with automatic update checks.

sudo ./dcc-downloader --background-task --auto-update <artifact_name>
Requires administrator / root
03 / CONTROLLED UPDATE

Request an update

Ask the installed service to perform a safe transactional update of its artifact.

sudo ./dcc-downloader --request-update <artifact_name>
Rollback-aware activation

TRUST THE ARTIFACT

Verification happens before activation.

The endpoint is intentionally static: no discovery API, no server-side installer, and no hidden package resolution. The artifact identifier is treated as an explicit operational input.

INTEGRITY PIPELINE

Signed manifest, verified archive

The downloader pins its verification material, validates the signature covering the checksum, then compares the downloaded archive with its SHA-256 digest before extraction.

01 / FETCHChecksum + signature
02 / VERIFYSignature + SHA-256
03 / ACTIVATEExtract or install
OPERATIONAL BOUNDARY

Know what the tool changes

  • One-time mode extracts into the current directory.
  • Managed mode creates a namespaced dccore-* service.
  • Machine state is kept in a dedicated downloader directory.
  • A failed integrity check prevents installation or activation.

SAFE REMOVAL

Remove one service—or uninstall everything.

For a single artifact, use the downloader’s native removal command. For machine decommissioning, the guarded uninstaller discovers every DC Core downloader service and removes only downloader-owned state.

FULL DOWNLOADER CLEANUP

A guarded exit path.

The removal script previews its scope, asks for confirmation, and uses the downloader’s native service teardown first.

  • Discovers only namespaced DC Core services and legacy tasks.
  • Preserves unrelated services, Scheduled Tasks, and crontab entries.
  • Stops before deleting state if any service cannot be removed.
  • Removal is destructive; review the dry run before continuing.

Linux full removal

Download and inspect the script, then preview it before the confirmed run.

curl -fsSL https://cud.dccore.io/remove-dcc-downloader.sh -o remove-dcc-downloader.sh
chmod +x remove-dcc-downloader.sh
less remove-dcc-downloader.sh
./remove-dcc-downloader.sh --dry-run
sudo ./remove-dcc-downloader.sh

A one-time downloader binary copied to an arbitrary working folder is not tracked. After the managed uninstall completes, delete that local copy manually if it is no longer required.

OPERATOR REFERENCE

The details that matter during a change.

Artifact identifiers are intentionally not listed by this endpoint. Use the value in your approved deployment configuration.

How do I remove only one managed artifact?

Run dcc-downloader --remove-background-task <artifact_name> with administrator or root privileges. This stops and unregisters that artifact’s service, then removes its installed binary and update state.

What changes when I use background mode?

The downloader persists a machine-scoped copy of itself, installs the requested artifact into downloader-owned state, and registers a dccore-<artifact> service with systemd or SysV on Linux, launchd on macOS, or the Service Control Manager on Windows.

What does auto-update mean?

--auto-update enables update checks when the managed service starts. --request-update writes a machine-scoped request that the running service consumes using its transactional update path.

What if verification fails?

Do not execute or activate the artifact. A signature or checksum failure is treated as an invalid download; the downloader exits without installing it.

Can the full uninstaller be automated?

Yes, after reviewing --dry-run on Linux/macOS or -WhatIf on Windows. Use --yes or -Yes only in an approved, non-interactive decommissioning workflow.

CLUSTER UPDATE DISTRIBUTION

Explicit inputs. Verified artifacts.
Controlled activation.

This endpoint provides immutable runtime files for approved DC Core bootstrap and upgrade operations. File names and layouts may change without notice.