pkg.soopen package index

brew / rank 9490

Install dory with Homebrew

Development proxy for docker. Version 1.2.0 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install dory

local Homebrew formula metadata

overview

Package summary

Development proxy for docker

Commands and aliases

  • dory

history

Project history and usage

Dory is a local development proxy for Docker-based projects. It combines a daemonized nginx proxy container, dnsmasq, and local resolver configuration so developers can reach containers by local domain names instead of IP addresses and ports.

Project history

The public FreedomBen/dory repository was created in March 2016. Its README explains that Dory wraps codekitchen/dinghy-http-proxy and makes it usable outside Dinghy, especially for teams mixing Docker for Mac and Dinghy workflows.

Dory's release history spans early 0.0.x tags through 1.2.0, while the RubyGems package page lists the same current version and a substantial historical download count. GitHub metadata shows the repository still receiving updates in 2026.

Adoption history

Dory was adopted through RubyGems and Homebrew, with the README recommending Homebrew on macOS and the Ruby gem on Linux. Its adoption niche is local web application development where Docker containers need stable, memorable hostnames.

How it is used

A common workflow installs Dory, sets `VIRTUAL_HOST` on containers, and runs `dory up`. Users can generate `~/.dory.yml` with `dory config-file`, then use commands such as `dory down`, `dory restart`, `dory status`, and `dory ip` to manage the proxy services.

Why package nerds care

Dory is package-nerd interesting because it packages a local development environment convention, DNS plus reverse proxy for Docker, as a small CLI that manages external services. It also reflects the Docker Machine, Dinghy, and Docker for Mac era of local container tooling.

Timeline

  • 2016: The public GitHub repository is created.
  • 2016: Early 0.0.x tags appear in the current repository.
  • 2020s: The package reaches the 1.x series.
  • 2026: GitHub metadata shows continued repository activity.

Related projects

  • Related projects include Docker, Docker for Mac, Dinghy, dinghy-http-proxy, nginx-proxy, dnsmasq, RubyGems, and Homebrew.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/.dory.yml<project>/.dory.yml

executables

Installed executables

CommandKindExposureNote
doryexecutableindexed executableDiscovered from the local executable index.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-08-03
manager version1.2.0
manager updated
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:dory
Version1.2.0
Package managerHomebrew
Homepagehttps://github.com/freedomben/dory
Repositoryhttps://github.com/FreedomBen/dory
Bottlenot recorded
Servicenone declared

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • pkg.so package database
  • pkgdb category and tag curation