dockerize

{
  "aliases": [],
  "alternatives": [],
  "build_dependencies": [
    "go"
  ],
  "categories": [],
  "caveats": null,
  "conflicts_with": [
    "powerman-dockerize"
  ],
  "dependencies": [],
  "deprecated": 0,
  "deprecation_reason": null,
  "desc": "Utility to simplify running applications in docker containers",
  "disable_reason": null,
  "disabled": 0,
  "enrichment_fetched_at": "2026-06-20T23:37:03+00:00",
  "first_seen": "2026-06-20T23:34:18+00:00",
  "full_name": "dockerize",
  "github_default_branch": "master",
  "github_last_commit_at": "2026-06-20T09:24:16Z",
  "github_readme_excerpt": "dockerize ![version v0.13.0](https://img.shields.io/badge/version-v0.13.0-brightgreen.svg) ![License MIT](https://img.shields.io/badge/license-MIT-blue.svg)\n=============\n\nUtility to simplify running applications in docker containers.\n\ndockerize is a utility to simplify running applications in docker containers.  It allows you to:\n* generate application configuration files at container startup time from templates and container environment variables\n* Tail multiple log files to stdout and/or stderr\n* Wait for other services to be available using TCP, HTTP(S), unix before starting the main process.\n\nThe typical use case for dockerize is when you have an application that has one or more configuration files and you would like to control some of the values using environment variables.\n\nFor example, a Python application using Sqlalchemy might not be able to use environment variables directly.\nIt may require that the database URL be read from a python settings file with a variable named\n`SQLALCHEMY_DATABASE_URI`.  dockerize allows you to set an environment variable such as\n`DATABASE_URL` and update the python file when the container starts.\nIn addition, it can also delay the starting of the python application until the database container is running and listening on the TCP port.\n\nAnother use case is when the application logs to specific files on the filesystem and not stdout\nor stderr. This makes it difficult to troubleshoot the container using the `docker logs` command.\nFor example, nginx will log to `/var/log/nginx/access.log` and\n`/var/log/nginx/error.log` by default. While you can sometimes work around this, it\u0027s tedious to find a solution for every application. dockerize allows you to specify which logs files should be tailed and where they should be sent.\n\nSee [A Simple Way To Dockerize Applications](http://jasonwilder.com/blog/2014/10/13/a-simple-way-to-dockerize-applications/)\n\n\n## Installation\n\nDownload the latest version in your container:\n\n* [linux/amd64](https:",
  "github_repo": "jwilder/dockerize",
  "github_stars": 5203,
  "github_topics": [
    "docker",
    "go"
  ],
  "homepage": "https://github.com/jwilder/dockerize",
  "homepage_og_description": null,
  "homepage_og_image": null,
  "homepage_title": null,
  "installs_30d": 139,
  "installs_365d": 1629,
  "installs_90d": 345,
  "keg_only": 0,
  "keg_only_reason": null,
  "last_seen": "2026-06-20T23:34:18+00:00",
  "license": "MIT",
  "llm_generated_at": null,
  "llm_model": null,
  "name": "dockerize",
  "oldnames": [],
  "one_liner": null,
  "optional_dependencies": [],
  "rank_30d": 3027,
  "rank_365d": 3086,
  "rank_90d": 3330,
  "raw_hash": "baa9d36eb19cfbc0",
  "recommended_dependencies": [],
  "revision": 0,
  "ruby_source_path": "Formula/d/dockerize.rb",
  "tap": "homebrew/core",
  "test_dependencies": [],
  "uses_from_macos": [],
  "version_head": "HEAD",
  "version_stable": "0.13.0",
  "versioned_formulae": [],
  "why_use_this": null
}