Discover gists

FreeBSD on Hetzner Cloud VPS

This guide explains how to install the FreeBSD on Hetzner Cloud VPS. This might also work for other VPS providers with the proper rescue system in place.

Table of contents:

1. Rescue mode
2. Download and deploy FreeBSD
3. Post-installation

1. Rescue mode

CTRL + D

Secilen satiri alt satiri kopyalar.

CTRL + /

Secilen satirlari comment icine alir. comment edilmisse commentten cikartir.

CTRL + w

Complete Recent Discord Quest

Note

This no longer works in browser!

Note

This no longer works if you're alone in vc! Somebody else has to join you!

How to use this script:

Accept the quest under User Settings -> Gift Inventory

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

Follow standard conventions.
Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
Boy scout rule. Leave the campground cleaner than you found it.
Always find root cause. Always look for the root cause of a problem.

Design rules

Learning Rust

The following is a list of resources for learning Rust as well as tips and tricks for learning the language faster.

Warning

Rust is not C or C++ so the way your accustomed to do things in those languages might not work in Rust. The best way to learn Rust is to embrace its best practices and see where that takes you.

The generally recommended path is to start by reading the books, and doing small coding exercises until the rules around borrow checking become intuitive. Once this happens, then you can expand to more real world projects. If you find yourself struggling hard with the borrow checker, seek help. It very well could be that you're trying to solve your problem in a way that goes against how Rust wants you to work.

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Have a look at git-conventional-commits , a CLI util to ensure these conventions and generate verion and changelogs

	----------POSSIBLE OPTIONS----------------------------------------------
	--account : [optional] account name to login with
	--key : [optional] connection key for the server (defaults to 1 in debug)
	--automationRoutine : [optional] automation routine to run after login
	--startAutomationGraph : [optional] start up and execute automation global graph using provided guid
	--gatherEffectStats : [optional] enables effect stat gathering
	--noautoconnect : [optional] Do not automatically connect to a server
	--fastQuit
	--dumpAssetNames : Write to <file> a JSON map of GUID (String "0xabc...") to asset name for all soft assets
	--startPosition : [optional] start position when joining a map

	#!/bin/bash
	# Install Latest XRDP with XORGXRDP and GFX/Glamor server-side acceleration
	# Tested on Ubuntu 22.04 LTS

	BUILD_DIR=/tmp/xrdpbuild
	echo "-> preparing $BUILD_DIR"
	rm -f -r $BUILD_DIR
	mkdir -p $BUILD_DIR

	# answer1.py

	import re

	def answer_1(dictionary: list):
	max_words = 0
	longest_str = ""
	pattern = r'[a-z][A-Z]'

	for string in Dictionary:

	{
	// miscellaneous
	"javascript.updateImportsOnFileMove.enabled": "always",
	"typescript.updateImportsOnFileMove.enabled": "always",
	"diffEditor.ignoreTrimWhitespace": false,

	// window
	"window.title": "🦙⚡🫡 – ${activeEditorShort}${separator}${rootName} – 🫡⚡🦙",
	"window.clickThroughInactive": false,