goliatone / envset Goto Github PK

Explore supporting dotenv configuration files.

It would be useful to be able to expand variables:

[development]
PATH = $PATH:/node_modules/.bin

OR

[development]
PATH = ${PATH}:/node_modules/.bin

See npm-run-path as a way to implement this.

To make envset files less verbose and less error prone, check each environment properties and make sure they have different values, if more than one environments have the same properties and values suggest to either move them to global or else is an error.

[development]
NODE_USERNAME=goliatone
NODE_PASSWORD=secret1

[production]
NODE_USERNAME=goliatone
NODE_PASSWORD=secret2

It wold suggest:

NODE_USERNAME=goliatone

[development]
NODE_PASSWORD=secret1

[production]
NODE_PASSWORD=secret2

Update docs:

envset <environment> -- <command>:

envset spawns a new process, attaches variables defined for to the process, and executes

We should handle errors on install.

Currently we run postinstall every time we install the package. If we are updating, we might now want to overwrite the config.

envsubst or this.

Handle error and give message explaining that the command was not found.

envset failed to execute provided command.
Ensure the following is a valid command.
slv docker-compose.tpl
{ Error: spawn slv ENOENT
    at exports._errnoException (util.js:1008:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
    at onErrorNT (internal/child_process.js:348:16)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)
    at Module.runMain (module.js:577:11)
    at run (bootstrap_node.js:352:7)
    at startup (bootstrap_node.js:144:9)
    at bootstrap_node.js:467:3
  code: 'ENOENT',
  errno: 'ENOENT',
  syscall: 'spawn slv',
  path: 'slv',
  spawnargs: [ 'docker-compose.tpl' ] }

If we run envset metdata generate in a repo that has no remote configured it fails:

2022/03/15 20:34:07 the key remote.origin.url is not found

We should really think if we want to delete this... what if we are just doing an upgrade?

If envset tries to execute a file without the right file perms it will throw this error:

{ [Error: spawn EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'spawn' }

suggest to user

If we try to run envset from a sub-directory in a project it will fail, do walk up the dir hierarchy to find conf.