This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.
To capture the video (filesize: 19MB), using the free "QuickTime Player" application:
A curated list of AWS resources to prepare for the AWS Certifications
A curated list of awesome AWS resources you need to prepare for the all 5 AWS Certifications. This gist will include: open source repos, blogs & blogposts, ebooks, PDF, whitepapers, video courses, free lecture, slides, sample test and many other resources.
FWIW: I (@rondy) am not the creator of the content shared here, which is an excerpt from Edmond Lau's book. I simply copied and pasted it from another location and saved it as a personal note, before it gained popularity on news.ycombinator.com. Unfortunately, I cannot recall the exact origin of the original source, nor was I able to find the author's name, so I am can't provide the appropriate credits.
// just an example. A cleaner way is to wrap the showLine-stuff in a dedicated component | |
<template> | |
<div> | |
<my-line v-if="showLine" :data="lineData" :options="options"> | |
</div> | |
</template> | |
<script> | |
export default { | |
data () { |
function checkForSWs() { | |
console.log('I will look for registered SW\'s now...') | |
navigator.serviceWorker.getRegistrations() | |
.then(sws => { | |
if (sws[0]) { | |
console.log('Found a registered SW:', sws[0], '\n Will proceed to unregister...'); | |
sws[0].unregister(); | |
console.log('Done.') | |
} else { | |
console.log('No registered SW\'s were found.') |
Sometimes, companies are worried about "reusing personal GitHub accounts", but contributing source code or reviews with an already existing account does NOT mean that
existing ssh keys or personal access tokens would be valid to access your enterprise organization (all credentials would have to be authorized: https://help.github.com/en/github/authenticating-to-github/authorizing-an-ssh-key-for-use-with-saml-single-sign-on)
email notifications would go to any personal email (you can enforce the use of a company email domain: https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/restricting-email-notifications-to-an-approved-domain)
contributions could not be marked to belong to your organization explicitly (you can explicitly mark contributions to be done on behalf of your company: https://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-on-behalf-of-an-organization)
you could not enforce any merged commit to satisfy your coding standards an
{ | |
"firestore": { | |
"rules": "firestore.rules", | |
"indexes": "firestore.indexes.json" | |
}, | |
"emulators": { | |
"firestore": { | |
"port": 8080 | |
} | |
} |