SomajitDey

# This function dumps the input stream to the path given as parameter.
# If PATH gets unlinked by another (cooperative) process, it creates a new file at PATH and continues dump
# Provide a lockfile as the 2nd positional parameter. This is needed so that another process doesn't remove PATH
# when it is being written to.

stream_dump(){
  declare -x path="${1}"
  local lock="${2}"
  local timeout="1" # Interval for polling $path
  declare -x line

SomajitDey

while num=$(read -re -p "type: "|& tee /dev/tty|fold -w "$(tput cols)"|wc -l); do tput cuu $num;tput ed; done

SomajitDey

How to use streambin for event-based workflow : pubsub (publish/subscribe) model

Push based workflow is more efficient than repeated pulls (polling). Thankfully, there is currently a free service for the same which is easy to use : https://streambin.pbedat.de/. There is also emitter.io and free, public MQTT brokers such as broker.hivemq.com (list).

1. Create a unique channel-key - it may be the hash of your email id or the hash of your MAC address, or may even be the fingerprint of freshly generated private-public keypair.

2. url="https://streambin.pbedat.de/streams/${channel_key}"

SomajitDey

Introduction

An introduction to curl using GitHub's API.

The Basics

Makes a basic GET request to the specifed URI

curl https://api.github.com/users/caspyin

SomajitDey

Updating a Gist or file using API is much faster (almost 3 times) than git-push

Git-push takes a lot of work figuring out what files need to be pushed. The local copy also needs to query upstream about its current state before it can decide whether a pull is necessary before push.

A local commit, on the other hand, takes almost no work compared to git-push.

Because Gist / file update using the REST API is nothing but a file-ransfer over https + a local commit@upstream, it is supposed to be faster than git-push.

Git-fetch is faster than git-push and is also better than download using API

SomajitDey

1. Create blob using API and extract its URL from the response using jq '.url'
2. Give the URL to anybody you wanna share the file with. All he needs to do is download

Since no commit is pointing to the blob, it doesn't present itself in your repository history and therefore, doesn't increase repo size.

SomajitDey

  key=<random but unique key> # Such as the hash of your email id!
  
  ########### Server:
  
  mkfifo pipe
  
  bash --rcfile <(echo 'PS0="$(tput cuu1; tput ed)"') -i <pipe |&
  curl -sf -N -T . https://pipeto.me/${key} >pipe
 

SomajitDey

Heroku Bash How-to

Heroku offers PaaS with a generous free-tier of 550 hours/month without requiring any credit-card validation. Official support is for Node.js, Python, Go, Ruby etc. But what if you just need to run a bash script, may be a netcat based server? Or you simply need to serve a webpage over http or https, and all you know is bash? (Of course you can also use the free services of x10hosting.com for the latter.)

Here are some simple steps to deploy a bash-script at Heroku.

1. Open a Heroku account
2. Download the Heroku CLI
3. git init the directory that contains your bash script
4. heroku login

SomajitDey

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

SomajitDey

#!/usr/bin/env bash
# Ref: https://unix.stackexchange.com/questions/159253/decoding-url-encoding-percent-encoding
# Ref: https://github.com/sixarm/urldecode.sh

input="${@//+/ }"
echo -e "${input//%/\\x}"