Amanbolat amanbolat

Steps to create the bootable USB

Create folder

mkdir autoinstall-ISO
cd autoinstall-ISO

Download ubuntu-autoinstall-generator

wget https://raw.githubusercontent.com/covertsh/ubuntu-autoinstall-generator/main/ubuntu-autoinstall-generator.sh

As claris/filemaker does its best to hide these links, here is a direct, non authenticated URL to download Filemaker Server 19/20 directly from Filemaker. Beware, their servers are slow.

FMS 19, Ubuntu 12

FMS 19, Ubuntu 20

https://downloads.claris.com/esd/fms_19.5.3.304_Ubuntu20.zip

How to find F# jobs

People often ask me how to find F# jobs. I don't have any special connections to companies using F#, and I don't have any special tricks either. I wish I did!

So, given that, here's my take on F# jobs.

Job hunting

For job hunting my suggestions are:

Using Git Commit Message Templates to Write Better Commit Messages

The always enthusiastic and knowledgeable mr. @jasaltvik shared with our team an article on writing (good) Git commit messages: How to Write a Git Commit Message. This excellent article explains why good Git commit messages are important, and explains what constitutes a good commit message. I wholeheartedly agree with what @cbeams writes in his article. (Have you read it yet? If not, go read it now. I'll wait.) It's sensible stuff. So I decided to start following the

Preparation

In open Ubuntu 18.04 machine click Parallels Actions -> "Install Parallels Tools"
A "Parallels Tools" CD will popup on your Ubuntu desktop.
Open it by double mouse click, copy all the content to a new, empty directory on a desktop, name it for e.g. "parallels_fixed"
Open terminal, change directory to parallels_fixed (cd ~/Desktop/parallels_fixed)
Make command line installer executable (chmod +x install)
Change directory to "installer" (cd installer)
Make few other scripts executable: chmod +x installer.* *.sh prl_*

Redis in Production at Smyte

To be clear we continue to run many Redis services in our production environment. It’s a great tool for prototyping and small workloads. For our use case however, we believe the cost and complexity of our setup justifies urgently finding alternate solutions.

Each of our Redis servers are clearly numbered with a current leader in one availability zone, and a follower in another zone.
The servers run ~16 different individual Redis processes. This helps us utilize CPUs (as Redis is single-threaded) but it also means we only need an extra 1/16th memory in order to safely perform a BGSAVE (due to copy-on-write), though in practice it’s closer to 1/8 because it’s not always evenly balanced.
Our leaders do not every run BGSAVE unless we’re bringing up a new slave which is carefully done manually. Since issues with the slave should not affect the leader and new slave connections might trigger an unsafe BGSAVE on the leader, slave Redis processes are set to not automatically rest

An Ansible summary

Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)

Configuration file

intro_configuration.html

First one found from of

	curl -I -k "https://api.github.com/repos/:owner/:repo/commits?per_page=1" \| sed -n '/^[Ll]ink:/ s/."next".page=\([0-9]\)."last".*/\1/p'

	### And that's all !
	# I saw many fighting with finding first commit SHA or similar fancy thing.
	# Here we just rely on the GH API, asking commits at 1 per page and parsing the last page number in the header of the reply (whose body only holds the last commit !)
	# So this is robust and bandwidth efficient. :)

	# If one want the commit count of a specific SHA, just use :
	curl -I -k "https://api.github.com/repos/:owner/:repo/commits?per_page=1&sha=:sha" \| sed -n '/^[Ll]ink:/ s/."next".page=\([0-9]\)."last".*/\1/p'

	// poller.go

	package main

	import (
	"fmt"
	"os"
	"os/signal"
	"time"