phgeraldeli

#! /usr/bin/env python
# -*- coding: utf-8 -*-
# python2.7

# ORIGINAL: https://gist.github.com/anjia0532/4a7fee95fd28d17f67412f48695bb6de

from requests import Request, Session
from requests.exceptions import RequestException
from datetime import datetime,timedelta
import urllib3

phgeraldeli

// Execute in jenkins script console

String saida = new ProcessBuilder( 'sh', '-c','''
  grep -A4 CredentialName credentials.xml | tail -1 | cut -d'>' -f2 | cut -d'<' -f1
  ''').redirectErrorStream(true).start().text

saida = saida.replaceAll('\\s','')

println( saida )
println( hudson.util.Secret.decrypt(saida) )

aymericbeaumet

Ever wanted to delete all your likes/favorites from Twitter but only found broken/expensive tools? You are in the right place.

1. Go to: https://twitter.com/{username}/likes
2. Open the console and run the following JavaScript code:

setInterval(() => {
  for (const d of document.querySelectorAll('div[data-testid="unlike"]')) {
    d.click()
 }

kenvontucky

image: node:latest

cache:
  key: ${CI_COMMIT_REF_SLUG}
  paths:
    - node_modules/

stages:
  - test
  - build

berkayunal

Loading variables from .env files in Ansible

Ansible has various ways of looking up data from outside sources, including plain text password files, CSV files and INI files. But it doesn't seem to have a lookup for .env files, as used in Laravel projects, also available for PHP, Ruby, Node.js, Python and others.

One option is to launch Ansible with the Ruby dotenv command line script... But that requires Ruby, which seems like overkill to me.

So here is a simpler solution that I use. It consists of:

1. The .env file itself
2. A small shell script that loads the .env file into environment variables - ansible-playbook.sh

h4cc

# Source: https://askubuntu.com/questions/912498/tl-wn722n-is-not-recognized

sudo apt-get install git dkms git make build-essential
cd /usr/src
sudo git clone https://github.com/lwfinger/rtl8188eu.git
sudo dkms add ./rtl8188eu
sudo dkms build 8188eu/1.0
sudo dkms install 8188eu/1.0
sudo modprobe 8188eu

renshuki

Install Terminator (shell)

sudo add-apt-repository ppa:gnome-terminator
sudo apt-get update
sudo apt-get install terminator

Terminator should be setup as default now. Restart your terminal (shortcut: "Ctrl+Alt+T").

Install ZSH

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions

bencz

#include <stdio.h>
#include <stdlib.h>

int main(void)
{
    int m = 0;
    double **a = 0;    
    int i = 0, j = 0, k = 0;	
    double factor = 0;	
    double temp = 0;