beastycoding

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

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

beastycoding

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.

1. Install Debian VM for each docker host
2. install Docker
3. Configure Docker Swarm
4. Install Portainer
5. Install KeepaliveD
6. glusterFS disk prep, install & config

beastycoding

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 $@

beastycoding

• 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 { 

beastycoding

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.

beastycoding

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;

beastycoding

- name: 'good first issue'
  color: '5319e7'
  description: 'Good for newcomers'
  aliases: []

- name: 'help wanted'
  color: '008672'
  description: 'Extra attention is needed'
  aliases: []

beastycoding

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

beastycoding

#!/bin/bash

for bucket in $(radosgw-admin bucket list | jq -r .[]); do
    bucket_id=$(radosgw-admin metadata get bucket:${bucket} | jq -r .data.bucket.bucket_id)
    marker=$(radosgw-admin metadata get bucket:${bucket} | jq -r .data.bucket.marker)
    for instance in $(radosgw-admin metadata list bucket.instance | jq -r .[] | grep "^${bucket}:" | grep -v ${bucket_id} | grep -v ${marker}| cut -f2 -d':'); do
         echo "${bucket}: ${instance}"
         radosgw-admin bi purge --bucket=${bucket} --bucket-id=${instance}
         radosgw-admin metadata rm bucket.instance:${bucket}:${instance}
    done

beastycoding

<?php

/**
 * Automatically login a single WordPress user upon arrival to a specific page.
 *
 * Redirect to home page once logged in and prevent viewing of the login page.
 * Compatible with WordPress 3.9.1+
 * Updated 2014-07-18 to resolve WP_DEBUG notice: "get_userdatabylogin is deprecated since version 3.3! Use get_user_by('login') instead."
 * Updated 2019-07-09 to reformat code, pass 2nd parameter to `do_action()`, and hook into priority 1.
 *