- Make sure you have a modern-ish version of Node.js installed.
- Type
npx https://gist.github.com/kfox/1280c2f0ee8324067dba15300e0f2fd3
- Connect to it from a client, e.g.
netcat
or similar:nc localhost 9000
https://filedn.com/lvm6y2PtpjGHDoBBMATwwLQ/rhel-atomic-installer-7.6.1.1-1.x86_64.iso |
// We'll use Puppeteer is our browser automation framework. | |
const puppeteer = require('puppeteer'); | |
// This is where we'll put the code to get around the tests. | |
const preparePageForTests = async (page) => { | |
// Pass the User-Agent Test. | |
const userAgent = 'Mozilla/5.0 (X11; Linux x86_64)' + | |
'AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.39 Safari/537.36'; | |
await page.setUserAgent(userAgent); |
FROM node:6-alpine | |
RUN apk update | |
RUN apk add --no-cache --virtual .gyp \ | |
python \ | |
make \ | |
g++ | |
COPY package.json /tmp/package.json | |
RUN cd /tmp && yarn | |
RUN apk del .gyp |
#!/bin/bash | |
# | |
# This script supports the following environment vars: | |
# - WEB_MEMORY: the amount of memory each | |
# process is expected to consume, in MB. | |
# - NODEJS_V8_ARGS: any additional args to | |
# pass to the v8 runtime. | |
# Replace this with the path to your main startup file. | |
# The `--color` flag ensures that any log output is |
# Docker Machine for Consul | |
docker-machine \ | |
create \ | |
-d virtualbox \ | |
consul-machine | |
# Start Consul | |
docker $(docker-machine config consul-machine) run -d --restart=always \ | |
-p "8500:8500" \ | |
-h "consul" \ |
dev_k8s(){ | |
local choice=$1 | |
K8S_VERSION=1.2.0 | |
if [ ! -f /usr/bin/kubectl ] && [ ! -f /usr/local/bin/kubectl ]; then | |
echo "No kubectl bin exists! Install the bin to continue :)." | |
return 1 | |
fi | |
if [[ $choice == "up" ]]; then |
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important
or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
This is where any fun you might have been having ends. Now it’s time to get serious and talk about rules.
Writing CSS is hard. Even if you know all the intricacies of position and float and overflow and z-index, it’s easy to end up with spaghetti code where you need inline styles, !important rules, unused cruft, and general confusion. This guide provides some architecture for writing CSS so it stays clean and ma
#!/bin/bash | |
mkdir -p /opt/bin | |
curl -L `curl -s https://api.github.com/repos/docker/compose/releases/latest | jq -r '.assets[].browser_download_url | select(contains("Linux") and contains("x86_64"))'` > /opt/bin/docker-compose | |
chmod +x /opt/bin/docker-compose |
$headers = 'From: Team Pasalubong <[email protected]>' . "\r\n"; | |
wp_mail('[email protected]', 'Test Mail After Purchase', 'TESTING', $headers); |