Learn how to send emails through Gmail SMTP with Cloudflare Email Routing in this comprehensive guide.
To proceed with this method, ensure that you have enabled two-factor authentication for your Google account. If you haven't done so already, you can follow the link to set it up → Enable 2FA in your Google account.
del v7.0.0 moved to pure ESM (no dual support), which forced me to move my gulpfile to ESM to be able to continue to use del.
The author sindresorhus maintains a lot of npm packages and does not want to provides an upgrade guide for each package so he provided a generic guide. But this guide is a bit vague because it's generic and not helping for gulp, hence this guide.
| #!/usr/bin/env bash | |
| set -e # exit on error | |
| ################################################ | |
| # | |
| # Prerequisits: | |
| # ensure ImageMagick is installed | |
| # | |
| # Usage: | |
| # convert-pdf2scan [--gray] files... | |
| # |
How to bring E-Mail retention policies to Gmail / Google Mail:
Inspired and adapted from Gmail Automation: 5 Useful Google Scripts to Automate Your Gmail
I'm still not sure what but on both my systems my keys just don't get loaded back into the ssh-agent on restarts and new login sessions. I got annoyed enough at it that I jumped through the hoops of putting ssh-add into a script and writting a property list file to load as a launchagent to fix it.
If you haven't done so already you can use the well written gub hub instructions for generating ssh keys. Once you get them generated you'll add them with ssh-add -K <sshkey> where sshkey is the file path/name. Keys are stored by default in your ~/.ssh folder
Note that you may need to use ssh-add --apple-use-keychain in Big Sur onward instead of ssh-add -K. I discovered the issue in Montery after skipping Big Sur.
The manual method (assuming your keys were stored into the Mac OS Keychain) is to open up Terminal
kubernetes 1.11.x(for example) versionhttps://stackoverflow.com/questions/52921122/homebrew-install-specific-version-of-formula
| # https://play.golang.org/p/JxqibtHkuO- | |
| func chunkBy(items []string, chunkSize int) (chunks [][]string) { | |
| for chunkSize < len(items) { | |
| items, chunks = items[chunkSize:], append(chunks, items[0:chunkSize:chunkSize]) | |
| } | |
| return append(chunks, items) | |
| } |
With the addition of ES modules, there's now no fewer than 24 ways to load your JS code: (inline|not inline) x (defer|no defer) x (async|no async) x (type=text/javascript | type=module | nomodule) -- and each of them is subtly different.
This document is a comparison of various ways the <script> tags in HTML are processed depending on the attributes set.
If you ever wondered when to use inline <script async type="module"> and when <script nomodule defer src="...">, you're in the good place!
Note that this article is about <script>s inserted in the HTML; the behavior of <script>s inserted at runtime is slightly different - see Deep dive into the murky waters of script loading by Jake Archibald (2013)
| #!/usr/bin/env bash | |
| # Functions to help handle STS manipulation of IAM credentials from | |
| # a shell console for AWS CLI, and other things - especially things | |
| # that don't support IAM roles being specific in boto profile config | |
| # | |
| # When you use the mfa() function, we assume that you do not have your | |
| # credentials defined with AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY | |
| # variables in the environment. The credentials must be configured elsewhere | |
| # in the boto search path such as ~/.aws/credentials or an EC2 Instance Profile |