Skip to content
This repository has been archived by the owner on Feb 28, 2020. It is now read-only.

Commit

Permalink
Merge pull request #72 from noisebridge/patrickod/add-readme-notice-e…
Browse files Browse the repository at this point in the history
…nv-file-encrypted

Add notice to README about encrypted .env file
  • Loading branch information
patrickod committed Oct 24, 2016
2 parents d0f0bad + b205264 commit d62404c
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions README.md
Expand Up @@ -23,6 +23,23 @@ bundle install
### Running with secrets
The secrets for the development environment are kept encrypted in the `.env` file. `git-crypt` will unlock them.

**NB: You must be aded to the list of secrets users before you can decrypt the .env file**

If you don't have access to the decrypted `.env` file locally you'll likely see
an error like so when you attempt to attempt to run the Rails console or server
locally.
```
/home/patrickod/.rbenv/versions/2.3.0/lib/ruby/gems/2.3.0/gems/dotenv-2.1.1/lib/dotenv/parser.rb:44:in `split': invalid byte sequence in UTF-8 (ArgumentError)
```

This is because `dotenv` is attempting to parse a non-ASCII file (the
encrypted blob). Simply `rm .env` to remove the local copy. If you want to run
with local development Stripe API credentials for the Noisebridge account ask
@patrickod to add you to the list of PGP keys that can decrypt the `.env` file.


####

To run the rails server locally with the secrets loaded use `foreman start web`

### Running without secrets
Expand Down

0 comments on commit d62404c

Please sign in to comment.