README setup has incorrect file paths for users who set up using Stripe cli

[chamm-stripe]

The readme contains several references to a node subdirectory that should exists under server, e.g.

cp .env.example server/node/.env

These paths do not work for users who setup using the cli option; the boilerplate created by the cli omits the node subdirectory, promoting the node.js files directly under server like so:

> ls server/    
README.md         node_modules      package-lock.json package.json      server.js

[cjavilla-stripe]

Thanks for reporting. There's a known difference between how the sample is cloned vs how it's used with the Stripe CLI. If you've previously logged in with the Stripe CLI (stripe login), then the .env file should be created for you automatically with your API keys set.