[feat] add config:push / config:pull for working with config vars about piku HOT 6 CLOSED

This is what the ENV file is for. What is the advantage here?

from piku.

Can't use ENV file to keep secrets, as it's committed to git. Therefore, I'm using a separate .env.prd file with both secrets and non-secret vars. Basically, the goal is to have piku set read vars from a file, instead of only command line.

from piku.

Perhaps the solution is to document the technique mentioned in #302

piku config:set `cat .env.prod`

This seems about as easy to remember and type as the Heroku oneliner you posted.

from piku.

If that would work properly, yes. Issues:

1. vars with spaces don't work (I'm using bash with Fedora 38). Tried with and without quotes:

 cat .env.test 
TEST1=t112


TEST2="t22 cd"

$ piku config:set `cat .env.test`
Piku remote operator.

Setting TEST2="t22 for 'app'
Error: malformed setting 'cd"'

2. (minor) Comments don't work -- lines starting with #

Seems it would be more reliable for piku to be able to read from a file, independent of what the current shell is set to.

from piku.

This issue is stale because it has been open for 90 days with no activity.

from piku.

This issue was closed because it has been inactive for 30 days since being marked as stale.

from piku.