How to use letsencrypt to generate ssl certificates and keys locally for any domain you own, using DNS entries for domain ownership validation.
- aws keys with rights to read/write AWS Route53 for the domain in question
- bash
Great Resource: http://www.json.org/js.html | |
// 99% of the time, you will want to be digest a json string from rails and read it into a javascript object. | |
response = JSON.parse(myJSONtext); | |
// then you can call the hash keys like they were methods | |
response.md5sum | |
response.file_name | |
// a reviver could be used as a pre-processor sort of, usually it will be left off. |
# A sample Gemfile | |
source "https://rubygems.org" | |
gem "capistrano" | |
gem "capistrano-node-deploy" |
# This is Git's per-user configuration file. | |
[user] | |
name = Nelbo Baggins | |
email = [email protected] | |
[alias] | |
shove = "!git push --set-upstream origin \"$(git rev-parse --abbrev-ref HEAD)\"" |
{ | |
/* Visit https://firebase.google.com/docs/database/security to learn more about security rules. */ | |
"rules": { | |
".read": "auth != null && auth.provider == 'anonymous' && auth.uid == 'SERVICE-ACCOUNT-CLIENT-ID'", | |
".write": "auth != null && auth.provider == 'anonymous' && auth.uid == 'SERVICE-ACCOUNT-CLIENT-ID'" | |
} | |
} |
I hereby claim:
To claim this, I am signing this object:
This is your tech spec’s abstract: the who/what/when/where/why of your entire proposal, made succinct. One or two sentences, keep it brief.
Contextualize your project: