{"id":13815548,"url":"https://github.com/markround/tiller","last_synced_at":"2025-05-15T09:32:26.041Z","repository":{"id":18766218,"uuid":"21979018","full_name":"markround/tiller","owner":"markround","description":"A dynamic configuration file generation tool, particularly useful with Docker containers","archived":false,"fork":false,"pushed_at":"2023-07-09T10:54:09.000Z","size":815,"stargazers_count":321,"open_issues_count":20,"forks_count":37,"subscribers_count":10,"default_branch":"master","last_synced_at":"2025-04-27T15:24:00.669Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Ruby","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/markround.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null}},"created_at":"2014-07-18T12:04:49.000Z","updated_at":"2025-01-24T05:47:49.000Z","dependencies_parsed_at":"2024-01-13T22:22:52.480Z","dependency_job_id":"70121d16-63d1-453f-84fd-36d6a651d5d3","html_url":"https://github.com/markround/tiller","commit_stats":{"total_commits":440,"total_committers":13,"mean_commits":33.84615384615385,"dds":0.3727272727272727,"last_synced_commit":"a246b2e7362ac539f63885239da481bad76752b0"},"previous_names":[],"tags_count":58,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/markround%2Ftiller","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/markround%2Ftiller/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/markround%2Ftiller/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/markround%2Ftiller/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/markround","download_url":"https://codeload.github.com/markround/tiller/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":254313883,"owners_count":22050125,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-04T04:03:34.930Z","updated_at":"2025-05-15T09:32:25.603Z","avatar_url":"https://github.com/markround.png","language":"Ruby","funding_links":[],"categories":["General Purpose Preprocessor","Ruby"],"sub_categories":["Snippets Manager"],"readme":"# What is it?\nTiller is a tool that generates configuration files. It takes a set of templates, fills them in with values from a variety of sources (such as environment variables, Consul, YAML files, JSON from a webservice...), installs them in a specified location and then optionally spawns a child process.\n\nYou might find this particularly useful if you're using Docker, as you can ship a set of configuration files for different environments inside one container, and/or easily build \"parameterized containers\" which users can then configure at runtime. \n\nHowever, its use is not just limited to Docker; you may also find it useful as a sort of \"proxy\" that can provide values to application configuration files from a data source that the application does not natively support. \n\nIt's available as a [Ruby Gem](https://rubygems.org/gems/tiller), so installation should be a simple `gem install tiller`.\n\n[![Gem Version](https://badge.fury.io/rb/tiller.svg)](http://badge.fury.io/rb/tiller)\n[![Build Status](https://travis-ci.org/markround/tiller.svg?branch=develop)](https://travis-ci.org/markround/tiller)\n![](https://img.shields.io/gem/dt/tiller.svg)\n [![Join the chat at https://gitter.im/markround/tiller](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/markround/tiller)\n[![Documentation Status](https://img.shields.io/badge/docs-latest-brightgreen.svg?style=flat)](http://tiller.readthedocs.io/en/latest/)\n\n# Documentation\nThe main documentation has been updated and a searchable, easy to read version is now hosted on [readthedocs.io](http://tiller.readthedocs.io/). You can also read the raw markdown files by browsing the [docs](docs/) directory in this repository.\n\nYou may like to read the [Quickstart](http://tiller.readthedocs.io/en/latest/quickstart/) guide if you want a very quick overview.\n\nThere is also a [Gitter chatroom](https://gitter.im/markround/tiller) for you to ask any questions, suggest new features and talk to other users.\n\n# Status\n\nOK, real talk here. This project has more-or-less stalled. I hesitate to say \"abandoned\" because I still care about it, but I have to be honest with anyone who might be looking at using it. The thing is, my life has had a number of (positive!) changes recently such as becoming a Dad, which have led to my free project time being greatly reduced. \n\nAlso, due to job changes and the changing technology landscape I now find myself involved in, I haven't actually used Tiller for several years. On top of that, I have realised that there are several fundamental issues with Tiller that I should tackle: Things like a re-write in Golang to avoid having to drag in a full Ruby/Gem environment for the runtime, and I also now believe that the top-level construct should be the file, and not the template that generates it. This would mean, for example, that having multiple files generated from the same template would be a very simple operation. The problem with all that is again lack of time, and the fact that I _really_ hate Go as a programming language.\n\nSo where does this leave the project ? Well, it _does_ work and has been battle-tested over many years. Some of the extra plugins such as Consul have badly stagnated however, and no longer work with current versions of libraries/APIs. If it works for you, then great! If you're looking for updates and a fancy Tiller 2.0 then I'm afraid you're going to be kept waiting. I'm not going to say \"never\" because I do still have a lot of love for this project; it was the first real open-source project I made that attracted a bunch of users, contributions and a small community around it which I'll always be thankful for. \n\nBut I guess it's best for everyone if you consider it \"done\" and what you see is what you get. If anyone is interested in forking it and producing a \"Tiller - The Next Generation\" then by all means give me a shout and I'll update things with links and pointers to your project but I won't be transferring ownership/RubyGems.org ownership etc. in the interests of security.\n\nThanks again for everything, and stay safe out there.\n\n-Mark Dastmalchi-Round, August 2020","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmarkround%2Ftiller","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fmarkround%2Ftiller","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fmarkround%2Ftiller/lists"}