Mohammad Raska Adekabang

# Resize the file system in UI, under VM -> Hardware -> Click on the disk to resize, click "Resize disk" button

# Confirm increase in disk space (1TB in my case)
$ lsblk
NAME                      MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda                         8:0    0    1T  0 disk
├─sda1                      8:1    0    1M  0 part
├─sda2                      8:2    0    1G  0 part /boot
└─sda3                      8:3    0    1T  0 part

Theory:

your git repository can have more than one remote server; In this case we want to have two:

one for our private repository on gitlab (will be the default one, called origin)
one to be connected to the source repo on github, to be able to pull new changes (will be called upstream)

How to make a private fork from github to gitlab

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.

	#!/bin/sh
	# install tools
	apt update -y && apt install nano wget curl libguestfs-tools -y
	# remove old image
	rm -rfv current/noble-server-cloudimg-amd64.img
	# remove old template container - WILL DESTROY COMPLETELY
	qm destroy 9000 --destroy-unreferenced-disks 1 --purge 1
	# download new image
	wget https://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img
	# add agent to image

	#!/usr/bin/env bash

	# Authorize to GitHub to get the latest release tar.gz
	# Requires: oauth token, https://help.github.com/articles/creating-an-access-token-for-command-line-use/
	# Requires: jq package to parse json

	# Your oauth token goes here, see link above
	OAUTH_TOKEN="34k234lk234lk2j3lk4j2l3k4j2kj3lk"
	# Repo owner (user id)
	OWNER="your-user-name"