Download the Router
The Router is a set of NuGet packages and a .NET tool on the Stella Ops NuGet feed.
Not released yet: no Router package is on the feed. The commands below work once the first release is published; until then this page shows how installation works.
Download terms: the Stella Ops Router packages and offline archives are subject to EU export controls and EU sanctions. They must not be downloaded, used or supplied in Russia or Belarus or for use in Russia or Belarus, or supplied to any person or entity in Russia or Belarus, nor for any other destination, end user or end use restricted by EU sanctions. Each package is provided under the LICENSE file it carries (The Router licence in plain words).
Before you start
- The .NET 10 SDK, to build a service or a gateway host with the packages.
- For the gateway tool: the .NET 10 runtime with ASP.NET Core.
Add the feed
Put a NuGet.config beside your solution. It takes every StellaOps.* package from the Stella Ops feed and every other package from nuget.org (package source mapping). Anyone can download from the feed; no account is needed.
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<packageSources>
<clear />
<add key="stellaops" value="https://nuget.stella-ops.org/v3/index.json" />
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
</packageSources>
<packageSourceMapping>
<packageSource key="stellaops">
<package pattern="StellaOps.*" />
</packageSource>
<packageSource key="nuget.org">
<package pattern="*" />
</packageSource>
</packageSourceMapping>
</configuration> Do not use the Stella Ops feed alone, for example with --source: its packages depend on packages from nuget.org, which it does not serve.
The installation guide covers the same steps in more detail: Installing Stella Ops packages: the feed, versions, signatures and the offline archive.
Install by role
Every package, its role and its licence: Router packages: which package serves which role, and its licence.
Service author
dotnet add package StellaOps.Microservice --prerelease
dotnet add package StellaOps.Microservice.SourceGen --prerelease
dotnet add package StellaOps.Router.Transport.Tcp --prerelease Replace Tcp with Tls, Udp, RabbitMq or Messaging for another transport.
Existing ASP.NET Core application
dotnet add package StellaOps.Microservice.AspNetCore --prerelease
dotnet add package StellaOps.Router.Transport.Tcp --prerelease Add the bridge and the client transport your gateway accepts.
Gateway operator
dotnet tool install StellaOps.Router.Gateway.Host --prerelease \
--tool-path /opt/stellaops/tools \
--add-source https://nuget.stella-ops.org/v3/index.json This installs the command stellaops-router-gateway into a folder for a system service, such as /opt/stellaops/tools; --global installs it for the current user instead. The tool carries every assembly it runs and has no package dependency.
Custom gateway host
dotnet add package StellaOps.Router.Gateway.Hosting --prerelease
dotnet add package StellaOps.Router.Transport.Tcp.Server --prerelease Add one server transport package for each transport your gateway accepts.
Tests and local development
dotnet add package StellaOps.Router.Gateway.LocalInMemoryHarness --prerelease
dotnet add package StellaOps.Router.Transport.InMemory --prerelease The harness runs only in the Development, Testing and Local environments.
Versions
- Every version has the form
x.y.z-yyyyMMddTHHmmssZ: the release number, then the UTC time of the release's first publication. All packages of one release share one version and are built from one commit: install them at the same version. - NuGet treats this form as a prerelease. Pass
--prereleaseto take the newest release, or--versionwith one exact version for a reproducible build. In Visual Studio, tick “Include prerelease”. - For reproducible builds, restore from a lock file: set
RestorePackagesWithLockFiletotruein the project and rundotnet restore --locked-modein CI. A published version never changes.
Check a package's signature
Every package is signed. NuGet does not check these signatures when it restores, so check them yourself when it matters. The release key signs the package keyring; the keyring lists each package key with its SHA-256, status and validity window; the package key signs the package. You need curl and openssl:
for f in cosign.pub nuget-signing-keys.txt nuget-signing-keys.txt.sig nuget-signing.pub; do
curl -sSLO "https://stella-ops.org/keys/$f"
done
sha256sum cosign.pub # 91481209caf0499d1063e2d5955bb5c151466a9258c0b4c2ec76e5db52e3409b
base64 -d nuget-signing-keys.txt.sig > ring.der
openssl dgst -sha256 -verify cosign.pub -signature ring.der nuget-signing-keys.txt
cat nuget-signing-keys.txt # id status valid-from valid-until file
sha256sum nuget-signing.pub # must equal the id of its keyring line
# one package: id and version in lower case
P=stellaops.microservice
V="<version in lower case>"
curl -sSLO "https://nuget.stella-ops.org/v3/flatcontainer/$P/$V/$P.$V.nupkg"
curl -sSLO "https://nuget.stella-ops.org/v3/flatcontainer/$P/$V/$P.$V.nupkg.sig"
base64 -d "$P.$V.nupkg.sig" > package.der
openssl dgst -sha256 -verify nuget-signing.pub -signature package.der "$P.$V.nupkg" Use the package key whose keyring status is not revoked and whose validity window holds the time in the package version. The same release key signs Stella Ops images and release bundles; the signing keys page describes every key.
Offline archive
A release can also be published as one archive, stellaops-nuget-router-<version>.tar.gz, with its SHA-256 in a .sha256 file beside it. Extracted, its packages/ folder is a local NuGet feed: every package of the release and every Stella Ops package they depend on, each with its signature, plus the public keys and the release record needed to check them without a network.
Compare the archive's SHA-256 with the published one, then point the stellaops source of your NuGet.config at the extracted packages/ folder. Third-party packages are not in the archive: keep nuget.org, or another source your organisation approves, for them.
No archive has been published yet.
