otty / dotfiles

All tools/NuGet

NuGet

nuget

NuGet is the package manager for .NET.

Detected by nuget | macOS, Linux, Windows |www.nuget.org

Sync it nuget.toml

Sync rules

What travels, what stays, what never leaves

NuGet in your home directory Every rule on this page, by file

<add key="globalPackagesFolder"<add key="repositoryPath"

Each machine keeps its own copy of these.

<add key="ClearTextPassword"<add key="Password"<add key="http_proxy.password"

Lifted into your secret store; the rest of the file syncs.

Only what the catalog names. A directory that syncs brings everything inside it except what is listed as excluded here.

apps/nuget.tomlThe file this page is generated from

id = "nuget"

name = "NuGet"

homepage = "https://www.nuget.org"

description = "NuGet is the package manager for .NET."

# nuget.org's own phrasing, trimmed: "the central package repository for

# NuGet, the package manager for .NET".

icon = "SimpleIcons:nuget"

detect = ["nuget"]

# https://learn.microsoft.com/en-us/nuget/consume-packages/configuring-nuget-behavior

# — the user-level config file is "Windows: %appdata%\NuGet\NuGet.Config

# Mac/Linux: ~/.config/NuGet/NuGet.Config or ~/.nuget/NuGet/NuGet.Config

# (varies by tooling)", and the same page says which of the two Unix spellings

# belongs to this entry: "These other tools look for the user config file under

# the ~/.config/NuGet folder: Mono, NuGet.exe, Visual Studio for Mac". The

# `nuget` command is NuGet.exe, so ~/.config/NuGet is its half; the

# ~/.nuget/NuGet spelling is the .NET CLI's and lives in the `dotnet` entry.

# ~/.config on macOS and Linux beside %APPDATA% on Windows is exactly the

# [configHome] base directory, so one line covers both.

paths = ["[configHome]/NuGet/NuGet.Config"]

exclude = []

# NuGet.Config is package sources and settings; the credentials inside it are

# carved out below rather than being the whole file.

secret = []

# Read once per command invocation, by a process that then exits.

side_effect = false

# https://learn.microsoft.com/en-us/nuget/reference/nuget-config-file,

# packageSourceCredentials: each source gets an `<add key="Username" …/>` and

# either `<add key="Password" …/>` (encrypted, Windows-only and machine-bound)

# or `<add key="ClearTextPassword" …/>`. The `config` section holds

# `http_proxy.password` on the same shape.

# NuGet.Config is XML, which this catalog's key_path syntax does not parse, so

# these are prefix rules — the tooling writes one `<add key=… />` element per

# line. They catch what `nuget sources add -username -password` writes; a

# hand-reflowed file, and the `<apikeys>` section (whose keys are source URLs

# and so cannot be named by a prefix), are past what a line rule can reach.

[[secret_paths]]

file = "[configHome]/NuGet/NuGet.Config"

match = { prefix = [

"<add key=\"ClearTextPassword\"",

"<add key=\"Password\"",

"<add key=\"http_proxy.password\"",

] }

# globalPackagesFolder and repositoryPath are absolute paths into this

# machine's disk layout; the same file on another machine needs its own.

[[machine_lines]]

file = "[configHome]/NuGet/NuGet.Config"

match = { prefix = [

"<add key=\"globalPackagesFolder\"",

"<add key=\"repositoryPath\"",

] }

Use it with your dotfile manager

Same data, in the shape your tool already reads

Opens Otty and adds this tool to what it syncs

Opens otty://sync/add/nuget. Otty ships with this catalog, so the link only has to name the tool — nothing is downloaded.

Every one of these is generated from the same rules as this page. None of them splits <add key="globalPackagesFolder" and <add key="repositoryPath" for you — that part is Otty’s own sync, or a template you write by hand.