zaiste

Using PostgreSQL's COPY to import & export CSV files

COPY can read/write data not only from/to CSV, but also from/to binary files. For the import, the table must exist along with its columns matching CSV columns.

Export table to CSV

COPY <table> TO 'file.csv' DELIMITER ',' CSV HEADER; 

zaiste

FILES=*.rst
for f in $FILES
do
  filename="${f%.*}"
  echo "Converting $f to $filename.md"
  `pandoc $f -f rst -t markdown -o $filename.md`
done

zaiste

Bank Name	SWIFT/BIC Code
ALIOR BANK	ALBPPLPW
ALIOR Sync	ALBPPLPW
ABN AMRO BANK	ABNAPLPW
ALLIANZ BANK	ALLBPLPW
CREDIT AGRICOLE	AGRIPLPR
BANK POLSKIEJ SPÓŁDZIELCZOŚCI	POLUPLPR
BPH	BPHKPLPK
BGŻ (Bank Gospodarki Żywnościowej)	GOPZPLPW

zaiste

Node.js Child Processes using spawn, exec, fork & async/await

Blog post: https://zaiste.net/nodejs-child-process-spawn-exec-fork-async-await/

Node.js runs in a single thread. You can, however take advantage of multiple processes.

child_process module allows to create child processes in Node.js. Those processes can easily communicate with each other using a built-in messaging system.

zaiste

#!/bin/bash

set -e

mkdir -p $HOME/bin $HOME/src
cd $HOME/src

wget https://github.com/tmux/tmux/releases/download/2.6/tmux-2.6.tar.gz 
wget https://github.com/libevent/libevent/releases/download/release-2.1.8-stable/libevent-2.1.8-stable.tar.gz 
wget https://ftp.gnu.org/pub/gnu/ncurses/ncurses-6.0.tar.gz

zaiste

const { compile } = require('pure-engine')
const escape = require('escape-html')
const fs = require('fs-extra');

async function example() {
  const content = await fs.readFile('./index.html');
  const { template } = await compile(content.toString())
  console.log(template({ foo: 'bar' }, escape))
}

zaiste

class String
  def unindent
    gsub(/^#{scan(/^\s*/).min_by{|l|l.length}}/, "")
  end
end

def display
  text = <<-TEXT.unindent
  Lorem ipsum dolor sit amet,
     consectetur adipisicing elit,

zaiste

Creating Secure REST APIs in Node.js without JWTs

Before we go on creating an actual RESTful API, let's address the elephant in the room: how to make an HTTP endpoint sufficiently secure in Node.js ?

I say sufficiently because, the topic of security is broad and constantly evolves. This article is a response to other Node.js articles I've seen that contain security mistakes. It may not be perfect, either, but is hopefully a good evolution on the topic.

Check the full article.

zaiste

zaiste

const Szelmostwo = require('./');
const { ok, json, created } = require('./response');

const { serve, security } = require('./middleware');

const app = new Szelmostwo();

app.get(
  '/',
  security(),