A newer version of this info is available at https://badcfe.org/how-to-paxton-with-rfidler/
Paxton fobs and readers are popular in the UK especially the Net2 system where the fobs look like this with a blue ring:
Paxton readers often look like this:
A collection of links to the excellent "Composing Software" series of medium stories by Eric Elliott.
| <? | |
| // | |
| // [ BUY BTC & ETH DAILY ON BITSTAMP ] | |
| // by @levelsio | |
| // | |
| // 2017-08-23 | |
| // | |
| // 1) buy $40/day BTC | |
| // 2) buy $10/day ETH | |
| // |
This cheat sheet provides a detailed overview of the exposed lifecycle events and available commands (and entrypoints) of the Serverless framework, that can be hooked by plugins (internal and external ones). The document is structured by the commands invoked by the user.
Lifecycle events are shown as the globally available outer events (all providers) and sub lifecycle events that are provider specific in the called order. Currently only the AWS provider is shown. If you have information about the other provider,
paymentModelFunction = function(gbHours, telemReports, downloadedBytes) {
gbHoursScaled = (gbHours - mean(gbHours)) / sd(gbHours)
telemReportsScaled = (telemReports - mean(telemReports)) / sd(telemReports)
downloadedBytesScaled = (downloadedBytes - mean(downloadedBytes)) / sd(downloadedBytes)
basePayout = 10
ghHourPayout = 12.2221 * gbHoursScaled
telemReportsPayout = 0.1452 * telemReportsScaled
| resources: | |
| Resources: | |
| IamRoleLambda: | |
| Type: 'AWS::IAM::Role' | |
| Properties: | |
| AssumeRolePolicyDocument: | |
| Version: '2012-10-17' | |
| Statement: | |
| - | |
| Effect: Allow |
| #!/usr/bin/env ruby | |
| # | |
| # Cloudsearch export script | |
| # | |
| # Required ENV Variables | |
| # * AWS_ACCESS_KEY_ID | |
| # * AWS_SECRET_ACCESS_KEY | |
| # * CS_SEARCH_ENDPOINT | |
| # * OUT_FILENAME | |
| # |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| let Thing = (props) => ( | |
| <div>look {props.name}! no state!</div> | |
| ) | |
| render(<Thing name="Ma"/>, el) |