peschee

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>co.echo.httpdfwd</string>
    <key>ProgramArguments</key>
    <array>
        <string>sh</string>
        <string>-c</string>

peschee

Available Public Wildcard DNS Domains pointing to localhost (127.0.0.1)

It turns out that some kind hearted people already set up wildcard domains for you already. You can use any domain below and/or any subdomain of these and they currently resolve to 127.0.0.1 but could switch at any time to resolve somewhere else. Here's the list of ones I know about. Let me know if there are more!

• localhost - It will always works. Do you know why? I hope so.
• [*.]fuf.me - Managed by @fidian; it will always point to localhost for IPv4 and IPv6
• [*.]fbi.com - 👏 👏 👏 👏 👏
• [*.]localtest.me
• [*.]127-0-0-1.org.uk
• [*.]vcap.me

peschee

Pure ESM package

The package linked to from here is now pure ESM. It cannot be require()'d from CommonJS.

This means you have the following choices:

1. Use ESM yourself. (preferred)
   Use import foo from 'foo' instead of const foo = require('foo') to import the package. Follow the below guide.
2. If the package is used in an async context, you could use await import(…) from CommonJS instead of require(…).
3. Stay on the existing version of the package until you can move to ESM.

peschee

class MyElement extends LitElement {
  
  // Promise that will resolve when the entire subtree of the element's `renderRoot` has finished updating/rendering.
  get updateSubtreeComplete() {
      async function awaitSubtree(el) {
        await el.updateComplete;
        const clients = el.renderRoot!.querySelectorAll('*');
        await Promise.all(Array.from(clients).map((e) =>
          e.updateSubtreeComplete || awaitSubtree(e as UpdatingElement)));
      }

peschee

import { directive } from "https://unpkg.com/@polymer/lit-element/lit-element.js?module"

const stateMap = new WeakMap()

export const tagProps = directive((tag, props = {}) => part => {
    let state = stateMap.get(part)
    const el = () => document.createElement(tag)
    if (state === undefined) {
        state = { tag, element: el() }
        stateMap.set(part, state)

peschee

#!/usr/bin/env bash

: ' Script that enables TLS for Docker service in Ubuntu 16.x

    This script is intended to be run as root

    It;

    - Generates the keys
    - Creates the daemon.json Docker config file

peschee

/**
 * This file provides common stuff to be used in the pipelines.
 * It is important to load it after repo checkout is done: see https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#triggering-manual-loading
 *
 */

/**
 * Dumps some info about the environment.
 * @return
 */

peschee

How to install a basic Apache, PHP and MySQL development environment with Homebrew

This guide will walk you through the steps required to install a basic Apache, PHP and MySQL development environment using homebrew. Basically, all you'll need to do is copy the commands below into Terminal. Copy one block at a time.

NOTE: this guide is mirrored from Echo & Co.'s blog in case the original blog post or the website decides to go down. I've shared this guide around many times to colleagues and friends. Please give Alan Ivey (@alanthing) all of the credit for publishing this really helpful guide.

Before we begin...

We're going to need to install homebrew, a super awesome package manager for OS X. Installation instructions are available on the homebrew website.

peschee

FROM gliderlabs/alpine:3.3
COPY myawesomescript /bin/myawesomescript
COPY root /var/spool/cron/crontabs/root
RUN chmod +x /bin/myawesomescript
CMD crond -l 2 -f

peschee

Sometimes you need to keep two upstreams in sync with eachother. For example, you might need to both push to your testing environment and your GitHub repo at the same time. In order to do this simultaneously in one git command, here's a little trick to add multiple push URLs to a single remote.

Once you have a remote set up for one of your upstreams, run these commands with:

git remote set-url --add --push [remote] [original repo URL]
git remote set-url --add --push [remote] [second repo URL]

Once set up, git remote -v should show two (push) URLs and one (fetch) URL. Something like this: