fname VS compose-generator

After getting a feature request from a predefined template contributor, Compose Generator now brings a new command for creating a blank predefined service template to start from scratch with a template contribution much faster. The command only works in a development environment and is not included in the production version. Thus, you will have to clone the GitHub repo and build the Compose Generator executable by yourself using the build.bat / build.sh script.

Since the beginning, Compose Generator supports generating stacks from configuration files (Example configuration). With this update it supports remote configuration files. Compose Generator will download the config file from the url and parse it directly. You can pass a remote config file the same way as a file on disk, but as an url instead of the filepath: cg --config https://example.com/config.yml

Configuration file (config.json): Holds the metadata for a service template like name, label, questions, volumes, secrets, etc. in JSON format. Example file, json spec

Application deployment with Docker and Kubernetes is easier than ever before, but could it even be much faster and much more seamless? This is where Compose Generator comes into play by helping you with common Docker tasks with a command line interface. Article on Medium: https://medium.com/p/d4356d38922d Github Repo: https://github.com/compose-generator/compose-generator