- using Ansible command line:
ansible-playbook --connection=local 127.0.0.1 playbook.yml
- using inventory:
127.0.0.1 ansible_connection=local
ansible-playbook --connection=local 127.0.0.1 playbook.yml
127.0.0.1 ansible_connection=local
#! /bin/sh | |
GOOS=linux go build -o $2 "$1" | |
GOOS=linux go build -ldflags="-s -w" -o $2.-sw "$1" | |
upx -f --brute -o $2.upx $2 | |
upx -f --brute -o $2.-sw.upx $2.-sw | |
GOOS=linux gotip build -o $2.tip "$1" | |
GOOS=linux gotip build -ldflags="-s -w" -o $2.tip.-sw "$1" | |
upx -f --brute -o $2.tip.upx $2.tip |
FROM nginx:alpine | |
# stock verison from php:alpine image | |
# ensure www-data user exists | |
RUN set -x \ | |
&& addgroup -g 82 -S www-data \ | |
&& adduser -u 82 -D -S -G www-data www-data | |
# 82 is the standard uid/gid for "www-data" in Alpine | |
# http://git.alpinelinux.org/cgit/aports/tree/main/apache2/apache2.pre-install?h=v3.3.2 |
// Gulp module imports | |
import {src, dest, watch, parallel, series} from 'gulp'; | |
import del from 'del'; | |
import livereload from 'gulp-livereload'; | |
import sass from 'gulp-sass'; | |
import minifycss from 'gulp-minify-css'; | |
import jade from 'gulp-jade'; | |
import gulpif from 'gulp-if'; | |
import babel from 'gulp-babel'; | |
import yargs from 'yargs'; |
// Parsing arbitrary JSON using interfaces in Go | |
// Demonstrates how to parse JSON with abritrary key names | |
// See https://blog.golang.org/json-and-go for more info on generic JSON parsing | |
package main | |
import ( | |
"encoding/json" | |
"fmt" | |
) |
# Source internet | |
# Use at your own risk, test on localhost first | |
# Ovrride Default index.php | |
DirectoryIndex home.php | |
# Prevent access to some files | |
<FilesMatch "^(wp-config.php|readme.html|license.txt|README.md|.gitignore|.gitattributes|.htaccess|error_log)"> | |
Order allow,deny | |
Deny from all |
Use these rapid keyboard shortcuts to control the GitHub Atom text editor on macOS.
#!/bin/bash | |
#@cecekpawon - thrsh.net | |
sudo kextunload /System/Library/Extensions/CUDA.kext | |
sudo rm -rf /usr/local/cuda | |
sudo rm -rf /System/Library/StartupItems/CUDA | |
sudo rm -rf /System/Library/Extensions/CUDA.kext | |
sudo rm -rf /Library/Preferences/com.nvidia.cuda* | |
sudo rm -rf /Library/PreferencePanes/CUDA\ Preferences.prefPane | |
sudo rm -rf /Library/LaunchAgents/com.nvidia.CUDASoftwareUpdate.plist |
The goal of this is to have an easily-scannable reference for the most common syntax idioms in JavaScript and Rust so that programmers most comfortable with JavaScript can quickly get through the syntax differences and feel like they could read and write basic Rust programs.
What do you think? Does this meet its goal? If not, why not?
JavaScript:
# first: | |
lsbom -f -l -s -pf /var/db/receipts/org.nodejs.pkg.bom | while read f; do sudo rm /usr/local/${f}; done | |
sudo rm -rf /usr/local/lib/node /usr/local/lib/node_modules /var/db/receipts/org.nodejs.* | |
# To recap, the best way (I've found) to completely uninstall node + npm is to do the following: | |
# go to /usr/local/lib and delete any node and node_modules | |
cd /usr/local/lib | |
sudo rm -rf node* |