I hereby claim:
- I am frans-k on github.
- I am frans_k (https://keybase.io/frans_k) on keybase.
- I have a public key ASCOWC-MUgtWhVbSuQSE7ggK_vF_BJKyu73aDmRpTo4fLgo
To claim this, I am signing this object:
| # Resends failed records from S3 to Firehose. | |
| require 'zlib' | |
| BUCKET = '' | |
| PROFILE = '' | |
| REGION = '' | |
| DELIVERY_STREAM_NAME = '' | |
| ERROR_MANIFESTS_PREFIX = '' |
I hereby claim:
To claim this, I am signing this object:
| For my own reference, an edited version of https://github.com/ankane/shorts/blob/master/Securing-Emails-Rails.md | |
| # Securing User Emails in Rails | |
| The GDPR goes into effect next Friday. Whether or not you serve European residents, it’s a great reminder that we have the responsibility to build systems in a way that protects user privacy. | |
| Email addresses are a common form of personal data, and they’re often stored unencrypted. If an attacker gains access to the database or backups, emails will be compromised. | |
| This post will walk you through a practical approach to protecting emails. It works with [Devise](https://github.com/plataformatec/devise), the most popular authentication framework for Rails, and is general enough to work with others. |
| box: wercker/ubuntu12.04-ruby2.0.0 | |
| services: | |
| - wercker/postgresql | |
| build: | |
| steps: | |
| - bundle-install | |
| - rails-database-yml: | |
| service: postgresql |