vitorgalvao

-- AppleScript --

-- This example is meant as a simple starting point to show how to get the information in the simplest available way.
-- Keep in mind that when asking for a `return` after another, only the first one will be output.
-- This method is as good as its JXA counterpart.

-- Webkit variants include "Safari", "Webkit", "Orion".
-- Specific editions are valid, including "Safari Technology Preview".
-- "Safari" Example:
tell application "Safari" to return name of front document

facultymatt

{
  "directory": "components"
}

jonschlinkert

Markdown cheatsheet

(Also see [remarkable][], the markdown parser created by the author of this cheatsheet)

Table of contents

• Standard features
  • Headings
  • Paragraphs

• Breaks

tedmiston

/*
In the node.js intro tutorial (http://nodejs.org/), they show a basic tcp 
server, but for some reason omit a client connecting to it.  I added an 
example at the bottom.

Save the following server in example.js:
*/

var net = require('net');

trinitronx

#!/bin/sh
# 2021-12-09:
#   This script is no longer supported!
#   Apple broke all direct downloads without logging with an Apple ID first.
#   The number of hoops that a script would need to jump through to login,
#   store cookies, and download is prohibitive.
#   Now we all must manually download and mirror the files for this to work at all :'-(

OSX_VERS=$(sw_vers -productVersion | awk -F "." '{print $2}')

chriskief

upstream php {
    server unix:/var/run/php5-fpm.sock;
}

server {
    # enforce NO www
    server_name www.example.com;
    return 301 $scheme://example.com$request_uri;
}

gustavohenke

var svg = document.querySelector( "svg" );
var svgData = new XMLSerializer().serializeToString( svg );

var canvas = document.createElement( "canvas" );
var ctx = canvas.getContext( "2d" );

var img = document.createElement( "img" );
img.setAttribute( "src", "data:image/svg+xml;base64," + btoa( svgData ) );

img.onload = function() {

ratbeard

.rainbow-text {                                                                                                                                                                           
    -webkit-background-clip: text;
    -webkit-text-fill-color: transparent;
    background-image: -webkit-gradient(linear,  left top,  left bottom, 
        color-stop(0.00, red), 
        color-stop(16%, orange),
        color-stop(32%, yellow),
        color-stop(48%, green),
        color-stop(60%, blue),
        color-stop(76%, indigo),

iamsk

import requests

from db import db

"""
The Douban Group API which not display on http://developers.douban.com/wiki/?title=api_v2

Base url: https://api.douban.com/v2

Group info: /group/:id

domenic

Auto-deploying built products to gh-pages with GitHub Actions

This is a set up for projects which want to check in only their source files, but have their gh-pages branch automatically updated with some compiled output every time they push.

A file below this one contains the steps for doing this with Travis CI. However, these days I recommend GitHub Actions, for the following reasons:

• It is much easier and requires less steps, because you are already authenticated with GitHub, so you don't need to share secret keys across services like you do when coordinate Travis CI and GitHub.
• It is free, with no quotas.
• Anecdotally, builds are much faster with GitHub Actions than with Travis CI, especially in terms of time spent waiting for a builder.