Skip to content

Instantly share code, notes, and snippets.

View elgalu's full-sized avatar

Leo Gallucci elgalu

View GitHub Profile

Both things have been introduced recently, and let you access even private ec2 instances

  1. Without VPN
  2. No open SSH port
  3. Authentication / Authorization is fully delegated to IAM
# Assumes valid AWS Credentials in ENV
@graninas
graninas / What_killed_Haskell_could_kill_Rust.md
Last active July 31, 2024 07:07
What killed Haskell, could kill Rust, too

At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.


What killed Haskell, could kill Rust, too

What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.

Is Haskell dead?

@tw3
tw3 / protractor-download-helper.ts
Last active January 28, 2022 17:56
Helps read and compare files downloaded during a protractor e2e test
// <project_root>/e2e/protractorDownloads/protractor-download-helper.ts
import { browser } from 'protractor';
const fs = require('fs');
const path = require('path');
export class ProtractorDownloadHelper {
private readonly maxReadWaitTime = 10000; // 10 seconds
@krishpop
krishpop / rl-packages.md
Last active April 1, 2021 07:49
RL Packages and Implementations
@dikiaap
dikiaap / git-io-custom-url.md
Last active June 19, 2024 01:26
git.io custom URL

Update: As of 11 January 2022, git.io no longer accepts new URLs.

Command:

curl https://git.io/ -i -F "url=https://github.com/YOUR_GITHUB_URL" -F "code=YOUR_CUSTOM_NAME"

URLs that can be created is from:

  • https://github.com/*
  • https://*.github.com
@schlomo
schlomo / ...README.md
Last active July 21, 2017 14:30
Demo for UI testing with selenium based on Zalenium, see http://blog.schlomo.schapiro.org/2017/07/web-ui-testing-made-easy-with-zalenium.html for details
@angelo-v
angelo-v / jwt-decode.sh
Last active October 5, 2024 01:06
Decode a JWT via command line
# will not work in all cases, see https://gist.github.com/angelo-v/e0208a18d455e2e6ea3c40ad637aac53#gistcomment-3439904
function jwt-decode() {
sed 's/\./\n/g' <<< $(cut -d. -f1,2 <<< $1) | base64 --decode | jq
}
JWT=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWV9.TJVA95OrM7E2cBab30RMHrHDcEfxjoYZgeFONFh7HgQ
jwt-decode $JWT
@diemol
diemol / HowTo.md
Last active January 31, 2018 09:38
How to use a Firefox custom profile with https://github.com/seleniumhq/docker-selenium

Steps to follow in the host machine (most likely, your machine).

Create a Firefox Profile

Copy the created profile to a given folder

  • In OSX, the profiles are located at ~/Library/Application Support/Firefox/Profiles. Find where they are in your operating system.
  • In the profiles folder you will find the profile you just created, for this case we will use the folder name hcqx24zh.selenium.
  • Copy the profile to a folder called firefox in a given location. E.g.:
@dersam
dersam / behatbox
Created September 23, 2016 14:25
Start a docker machine for running tests via Webdriver with the elgalu/selenium container
#!/usr/bin/env bash
docker-machine start default
docker rm -f grid
docker run --rm --name=grid --add-host='develop.vagrant.dev:192.168.80.80' -p 4444:24444 -p 5920:25900 \
-v /dev/shm:/dev/shm -e VNC_PASSWORD=hola elgalu/selenium:2.51.0b > /dev/null &
sleep 5

Comparison of configuration file languages

We need to PEPify a static format for writing down bootstrap information in Python source trees. The initial target is a list of PEP 508 package requirement strings. It's possible that in the future we might want to add more features like a build system backend specification (as in PEPs 516, 517), or an extension namespace feature to allow third-party developer tools (flit, pytest, coverage, flake8, etc.) to consolidate their configuration in this file in a systematic