Lunitrixx lunitrixx

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

Flow of lua nginx module directives: https://openresty-reference.readthedocs.io/en/latest/Directives/
body_filter_by_lua documentation: https://github.com/openresty/lua-nginx-module#body_filter_by_lua
Following sample is from this site: https://groups.google.com/d/msg/openresty-en/5PWmL2f70x8/R2DUMsNUAgAJ

http { 
    proxy_cache_path /tmp/cache levels=1:2 keys_zone=cache:60m max_size=1G; 
    server { 
      listen 8080; 

      location /replace-body {

Agressive URL encode

Python based CLI tool to agressively url-encode strings, rather than just encoding non-url characters this tool will encode every character in the URL.

Usage:

Firstly make a function in your .bash_profile to call the script

function url-encode()
{
 python ~//url_encode.py $@

This (and related gists) captures how i created my docker swarm architecture. This is intended mostly for my own notes incase i need to re-creeate anything later! As such expect some typos and possibly even an error...

Installation Step-by-Step

Each major task has its own gist, this is to help with maitainability long term.

Proxmox VE Installation on Hetzner Server via Rescue System

Follow these steps to install Proxmox VE on a Hetzner server via the Rescue System. The Rescue System is a Linux-based environment that can be booted into to perform system recovery tasks. We'll be using it to install Proxmox VE.

In order to complete the process, it is indeed necessary to first boot into the Rescue System and then connect to it via SSH. This will allow you to run the commands for installing Proxmox VE. Here are the steps:

Starting the Rescue System

Log into the Hetzner Robot.
Under "Main Functions; Server" select the desired server and then open the tab "Rescue".

Proxmox Backup

At this time proxmox backup only backs up VM and Containers - ths guide covers that.

What i didn't realize is the backup job is still defined on the cluster and PBS provides a new storage type that dedupes and managed all the vzdump files created - which is cool.

I decided to run proxmox backup on my Synology NAS where it has more reliable connection to the NAS (i.e. via memory) for doing deduple, garbage collection, prune, verification etc. However the steps here generally remain true.

Once again i used one of Derek Seaman's Awesome Blogs for the basis of this - but with my own tweaks (like using SMB instead of CIFS. As of 9/21 my tweaks are signifcnant, in the original blog it is missing steps to enable encoding acceleration in CTs and VMs.

this gist is part of this series

How to use use Bitwarden CLI for SSH-Keys in macOS

If you want to use Touch ID have a look at: How to use use Bitwarden CLI with macOS Touch ID

Wirtten and tested on macOS Ventura

Add SSH-Keys to Bitwarden

Before you can use Bitwarden CLI for your SSH private keys you have to add them to your Bitwarden account. Just create a normal login. The name, username and URI fields doesn't matter for my functions.

	add_header Referrer-Policy origin always; # make sure outgoing links don't show the URL to the Matomo instance
	add_header X-Content-Type-Options "nosniff" always;
	add_header X-XSS-Protection "1; mode=block" always;

	location ~ \.php$ { ##delete##
	}

	## only allow accessing the following php files
	location ~ ^/(index\|matomo\|piwik\|js/index\|plugins/HeatmapSessionRecording/configs)\.php$ {
	try_files /e1fe7cea61d2bd1bde9a19b6a2993a8f.htm @php;

	version: '4.5'
	services:

	# GITLAB
	gitlab-web:
	image: 'gitlab/gitlab-ce:latest'
	restart: always
	container_name: gitlab-web
	hostname: '192.168.0.14'
	environment:

	zfs list -t snapshot -H -o name \| grep "201509[0-9].*" \| xargs -n1 echo
	# zfs list -t snapshot -H -o name \| grep "201509[0-9].*" \| xargs -n1 zfs destroy