Add a CLI wizard to help create and configure env variables

ShoppinPal / StockUp

StockUp [try it out at https://stockup-staging.shoppinpal.com] is the only open source product that delivers 100% automated replenishment, integrations with leading POS and ERPs, and a smooth web application that can be used by your entire Ops crew and external suppliers. Our customers have saved countless hours that would be otherwise lost in grappling with Excel, along with huge increase in accountability. Feel free to clone the project and write to us at stockup@shoppinpal.com with what you'd like to achieve and how we can help!

GNU General Public License v2.0

57 stars 22 forks source link

Add a CLI wizard to help create and configure env variables #268

Open pulkitsinghal opened 6 years ago

pulkitsinghal commented 6 years ago

It would be great if a CLI wizard asked all the relevant questions and then setup the following files: .env, worker.env, worker2.env

Its the next step in making things better.

So @harshadyeola, cCould this be something that you want to eventually delegate to @Bhushan001?

pulkitsinghal commented 6 years ago

Brainstorming ideas:

Maybe a JSON file can store description, keyName, defaultValue etc and that can be loaded into the CLI tool which then goes through all the keys and prompts the user to add a value or accept the default while showing the description as a hint about what the key/value pair does.

Ultimately the env file which would be saved can put description as comments and the key=value under it.

Some key value pairs which should be generated by terraform might require the cli wizard to spin off a child bash command which can still interact with the user and when it’s done then the input control goes back to the cli wizard

pulkitsinghal commented 6 years ago

Tools that come to mind

Nconf
envfile
caporal
vorpal

But still not sure about a framework that can start other bash commands as its children and resume control later in an effortless fashion.

harshadyeola commented 6 years ago

@pulkitsinghal Before we go ahead for any cli development, here is the following strategy I would like to mention that can work well.

We are setting up env files here and finally docker is using them to set env variables. but if we have to update any value for any env var we have to restart the containers. so what I will suggest here is modify our code such that it works like below
if .env file is present read the values from there
if it is not present then check for the env vars In this way we will be achieving following things
for dev environments it will be easier to update the vars values that will take away extra time needed to restart containers.
for prod environments we can setup env vars. cc @Bhushan001

harshadyeola commented 6 years ago

@pulkitsinghal Solved https://github.com/ShoppinPal/warehouse/pull/273