| var http = require('https'); | |
| var querystring = require('querystring'); | |
| // set the post request options | |
| var reqOptions = { | |
| hostname: 'hooks.slack.com', | |
| port: 443, | |
| path: '/services/YOUR/SLACK/HOOK_HERE', | |
| method: 'POST' | |
| }; |
| // You can defer the side-effect execution in middlewares | |
| const sideEffect = appState => dispatch => localStorage.setItem('counter', appState); | |
| function plainOldReducer(appState) { | |
| return appState + 1; | |
| } | |
| // Composition simply work | |
| function nestedReducer*(appState, action) { | |
| if (action === FOO) { |
| #!/usr/bin/env bash | |
| # | |
| # gh-dl-release! It works! | |
| # | |
| # This script downloads an asset from latest or specific Github release of a | |
| # private repo. Feel free to extract more of the variables into command line | |
| # parameters. | |
| # | |
| # PREREQUISITES | |
| # |
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
I am deploying with this IAM using Codeship and Circle CI to Elastic Beanstalk. I had a lot of trouble with this config. I talked to the aws support for about 6 hours until this worked properly, so, I guess it is worth to share.
UPDATE: In the end, I have to use the AWSElasticBeanstalkFullAccess policy. My custom policy keep breaking every week with some new added permission or some EB internal change. Anyway, the IAM I was using is below.
This works for me with CircleCI and EB Cli.
{
"Version": "2012-10-17",
"Statement": [
{
| 'use strict'; | |
| /* | |
| # FetchData | |
| If property callback `if(storeState)` return true, calls property callback | |
| `fetchData(dispatch, storeState)` so it may dispatch FETCH actions. | |
| ## Usage: |
| STACK:=myapp-dev | |
| TEMPLATE:=cloudformation-template_vpc-iam.json | |
| PARAMETERS:=cloudformation-parameters_myapp-dev.json | |
| AWS_REGION:=us-east-1 | |
| AWS_PROFILE:=aws-dev | |
| all: | |
| @which aws || pip install awscli | |
| aws cloudformation create-stack --stack-name $(STACK) --template-body file://`pwd`/$(TEMPLATE) --parameters file://`pwd`/$(PARAMETERS) --capabilities CAPABILITY_IAM --profile $(AWS_PROFILE) --region $(AWS_REGION) |
| // SPDX-License-Identifier: MPL-2.0 | |
| // AES Encryption/Decryption with AES-256-GCM using random Initialization Vector + Salt | |
| // ---------------------------------------------------------------------------------------- | |
| // the encrypted datablock is base64 encoded for easy data exchange. | |
| // if you have the option to store data binary save consider to remove the encoding to reduce storage size | |
| // ---------------------------------------------------------------------------------------- | |
| // format of encrypted data - used by this example. not an official format | |
| // | |
| // +--------------------+-----------------------+----------------+----------------+ |
Paid content makes up a significant portion of the content available online, especially high value content. Users who are seeking information via search engines frequently run queries for which the most relevant content is to be found from payment-required sources. However, in order that search crawlers are able to index this content, paid content publishers typically permit such crawlers to access their pages as if the crawler were a paid-up subscriber. As a result, search results displayed to users of search engines can create the expectation of free content and disappointment or frustration when the user is denied access.
To date, search providers have attempted to solve this problem by requiring content owners to make content available to searchers in the same form as it is available to the crawler, when a searcher clicks on a search result, a practice known as "First click free". In most cases it is a breach of the search provider's terms of service to bar se
An IAM user policy document to give minimal rights for deploying an Elastic Beanstalk application.
Where:
REGION: AWS region.ACCOUNT_ID: AWS account ID.APPLICATION_NAME: Desired target Elastic Beanstalk application name(space).IAM_INSTANCE_PROFILE_ROLE: The instance profile (IAM role) Elastic Beanstalk EC2 instaces will run under.