Peter Mikitsh

Should the module build be removed from the rollup config then?

Upgrading to Helm 3 will solve this problem. The tiller client is eliminated, so no need to generate certificates.

## Client-server model Before I began working on `snow`, I did my best to research alternatives. I, too, came across exoframe. The benefits of a client-server model look appealing: instead...

Supporting linux is going to be important for users wishing to use snow in ci-type environments, and all `snow` commands should work on Mac OS and Linux. 50,000 foot view:...

I'd also like to point out that the `snow create` [command](https://github.com/snowjs/cli/blob/secrets/src/create.ts#L173) relies on `openssl` being in the user's path, but we don't check for it in `snow install` -- but...

Another approach to this problem is to reduce the number of needed CLI dependencies. It's probably not feasible to remove all of Snow's CLI dependencies. However, substituting in some JS...

Per the good folks on the Kubernetes #helm-dev slack channel, the v3 pre-release is landing in a couple weeks too. Could be worthwhile to wait for that.

When I run the latest version of the `secrets` branch in a directory without a Dockerfile, this is the output I see: ``` $ snow Error finding Dockerfile. ENOENT: no...

Hi @nahtnam, I do not have instructions for DigitalOcean but I will add some this week. Hang tight, and thank you!

Thank you for the quick reply. I have enough information work to proceed on a PR. I did more research on Number 3: Bluebird's [homepage](https://github.com/petkaantonov/bluebird) has this to say on...