tegansnyder

I’m looking for any tips or tricks for making chrome headless mode less detectable. Here is what I’ve done so far:

Set my args as follows:

const run = (async () => {

    const args = [
        '--no-sandbox',
        '--disable-setuid-sandbox',
        '--disable-infobars',

Ariex

const Page = require('puppeteer/lib/Page');

// the following 2 methods are originally from: https://github.com/GoogleChrome/puppeteer/issues/85#issuecomment-341743259, with some modification to fit puppeteerv1.0.0
async function newPageWithNewContext(browser) {
    const { browserContextId } = await browser._connection.send('Target.createBrowserContext');
    const { targetId } = await browser._connection.send('Target.createTarget', { url: 'about:blank', browserContextId });
    const target = await browser._targets.get(targetId);
    const client = await browser._connection.createSession(targetId);
    const page = await Page.create(client, target, browser._ignoreHTTPSErrors, browser._appMode, browser._screenshotTaskQueue);
    page.browserContextId = browserContextId;

GuilloOme

(function() {
    'use strict';

    // keep track of all the opened tab
    let tabs = {};

    // Get all existing tabs
    chrome.tabs.query({}, function(results) {
        results.forEach(function(tab) {
            tabs[tab.id] = tab;

StevenACoffman

MicroService Proxy Gateway Solutions

Kong, Traefik, Caddy, Linkerd, Fabio, Vulcand, and Netflix Zuul seem to be the most common in microservice proxy/gateway solutions. Kubernetes Ingress is often a simple Ngnix, which is difficult to separate the popularity from other things.

Github Star Trend:

This is just a picture of this link from March 2, 2019

Originally, I had included some other solution

sararob

'use strict';

// Dependencies
const gcloud = require('google-cloud', {
  projectId: 'sara-bigquery',
  keyfileName: 'keyfile.json'
});
const vision = gcloud.vision();
const fs = require('fs');
const async = require('async');

dimkir

#!/bin/bash

DIST_DEPS=0
CENTOS_DEPS=0

GCONF_COMPILE=0
GCONF_INSTALL=0

PIXBUF_INSTALL=0
PIXBUF_COMPILE=0

dimkir

Running nightmare on Amazon Linux

You may have thought of running nightmare on AWS Lambda. But before we can run it on Lambda, we need first to make it run on Amazon Linux.

Provision instance which replicates Lambda environment

According to AWS Documentation on Lambda Execution Environment and available Libraries we would need this AMI image with this alias amzn-ami-hvm-2016.03.3.x86_64-gp2. Keep in mind that AMI-image-id for this instance would be different in different regions (eg):

• In eu-west-1 - ami-f9dd458a
• In us-east-1 - ami-6869aa05

LeCoupa

# Redis Cheatsheet
# All the commands you need to know


redis-server /path/redis.conf  # start redis with the related configuration file
redis-cli                      # opens a redis prompt


# Strings.

dbrent-amazon

Note that this is sandbox. If you have not registered profiles in sandbox you 
will need to do so prior to making these calls. You will also need at least 
one campaign, ad group, and keyword before you see anything in the report. 
While in sandbox, we will return “dummy” data so that you can see how an actual 
report would look.
 
To make it look nicer, I always export my access token prior to making calls. 
You could do the same for API-Scope (profile Id) if you wish. Make sure to use 
quotes around the access token if it isn’t URL encoded. It has a | (pipe) 
symbol and your shell won’t like it.

materkel

/**
 * Install and enable the rabbitmq_delayed_message_exchange plugin as described by Alvaro Videla in this blogpost:
 * https://www.rabbitmq.com/blog/2015/04/16/scheduling-messages-with-rabbitmq/
 */
const amqp = require('amqplib');
const exchange = 'yourExchangeName';
const queue = 'yourQueueName';
const queueBinding = 'yourQueueBindingName';

// Message consumer