config.yaml **not** generated after first use

[kkrieger85]

#Ref readme.md

The configuration of the script is done in ~/.config/sw-cli-tools/config.yaml. If the file does not exist on your system, it is created after the first usage of the script.

I tried to generate test data with sw:generate. This command doesn't work without config.yaml setting for Datagenerator/locale

After that I created a plugin with sw:plugin:create and no config.yaml was generated

[mitelg]

which OS do you use? where do you execute the cli-tools?

[kkrieger85]

ddev describe          
NAME       TYPE  LOCATION            URL                          STATUS        
shopware5  php   ~/htdocs/shopware5  https://shopware5.ddev.site  running

Project Information
-------------------
PHP version:   	7.2
MariaDB version	   
MySQL version  	   

URLs
----
http://shopware5.ddev.site 
http://127.0.0.1:32795     
https://shopware5.ddev.site
https://127.0.0.1:32794    

MySQL/MariaDB Credentials
-------------------------
Username: "db", Password: "db", Default database: "db"

or use root credentials when needed: Username: "root", Password: "root"

Database hostname and port INSIDE container: db:3306
To connect to db server inside container or in project settings files: 
mysql --host=db --user=db --password=db --database=db
Database hostname and port from HOST: 127.0.0.1:32782
To connect to mysql from your host machine, 
mysql --host=127.0.0.1 --port=32782 --user=db --password=db --database=db

I installed (and self-updated) sw.phar to ~/bin/sw (chmod +x ) via wget http://shopwarelabs.github.io/sw-cli-tools/sw.phar && mv sw.phar ~/bin/sw

[mitelg]

if you create the file by yourself, will it be read by the tool?

[kkrieger85]

Yes. I copy & paste config.yaml.dist to ~/.config/sw-cli-tools/config.yaml changed Dategenerator settings and this worked for me

[mitelg]

ok, nice to here that 👍

I will leave this issue open, so that one could have a look, why it is not auto generated in the first place

[kkrieger85]

From my point of view, there's no code, which should save a config file - maybe i overlooked this part

[mitelg]

😄 I'm not sure either. maybe we just have to adjust the readme file 😉

but as this is not a official supported repository, I don't know, when I have time to do it