markround/tiller

No configuration files present?

Opened this issue · 3 comments

$ gem --version
2.5.2

quickstart/templates/common.yml:

---
data_sources: [ "file" , "environment" ]
template_sources: [ "file" ]
environments:
  development:
    db.erb:
      target: db.ini

quickstart/templates/db.erb:

db_hostname: <%= env_db_hostname %>

in quickstart:

$ export DB_HOSTNAME=mydb.example.com
$ tiller --base-dir=./quickstart
tiller v1.2.0 (https://github.com/markround/tiller) github@markround.com
Error: No configuration files present!

Any help is appreciated to get someone up and running :)

Hi, the common.yml should be in the quickstart/ directory, not quickstart/templates/. Does this fix things ?

Hi Mark

No, after moving the common.yml from quickstart/templates one level up to quickstart and then

cd to home in my /Users/seb/

$ export DB_HOSTNAME=mydb.example.com

$ echo $DB_HOSTNAME
mydb.example.com

$ tiller --base-dir=./quickstart or
$ tiller --base-dir=./quickstart/

tiller v1.2.0 (https://github.com/markround/tiller) <github@markround.com>
Error: No configuration files present!

Mins-MacBook-Pro:~ mincheung$ tiller --base-dir=./quickstart/
tiller v1.2.0 (https://github.com/markround/tiller) <github@markround.com>
Error: No configuration files present!

It would helpful if documentation says where files are and in which directory should commands be executed, basically telling users how to structure our code would be great.

OK I guess the naming convention is common.yaml:

tiller -b . -e development
tiller v1.2.0 (https://github.com/markround/tiller) <github@markround.com>
Template generation completed

and NOT common.yml

$ tiller -b . -e development
tiller v1.2.0 (https://github.com/markround/tiller) <github@markround.com>
Error: No configuration files present!

as I have always used .yml and not .yaml in the past as I believe Win doesn't allow four letters file extensions but not issue anywhere else...

But unfortunately in most banking clients it is still predominately Win environment.... so how to resolve this?