If you're self-hosting your services and having trouble getting your emails through Gmail and infuriated by Google's non-existent support, you're not the only one. I'd like to share my experiences trying to get it sorted out.
I'm the author of the post above. You can tell how arrogant Google employees are from all the previous posts he made in the past.
| \documentclass[11pt, oneside]{article} | |
| \usepackage[margin=0.5in]{geometry} | |
| \geometry{letterpaper} | |
| \usepackage[parfill]{parskip} | |
| \usepackage{graphicx} | |
| \usepackage{amssymb} | |
| \usepackage{xcolor} | |
| \pagecolor{white} | |
| \usepackage[colorlinks = true, linkcolor = blue, urlcolor = blue]{hyperref} | |
| \pagestyle{empty} |
Virtualization is the conceptual technology on which modern services (server applications) are built. Whether an application happens to run on a fully- or para-virtualized VM[^2] or is containerized—or even runs on a “bare-metal” physical server after all—most modern services are designed in isolated, replicated, disposable components on commodity hardware.[^3] The [“twelve-factor methodology”][wiggins] (2011) is an influential articulation of the principles
The following grammar is based on this EBNF specifications for EBNF meta-grammar:
ebnf ::= [ global-desc ] { local-desc | rule | comment }
local-desc ::= '{' ? { any-character } ? '}'
global-desc :: "{{" ? { any-character } ? "}}"
rule ::= identifier '::=' expression [ '.' ]
This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.
Let’s begin.
First of all, there are some concepts that one must unlearn from ipv4:
Concept 1