Más información - Docs Oficiales
- Instalar TypeScript y tipos de Node, como dependencia de desarrollo
npm i -D typescript @types/node
- Inicializar el archivo de configuración de TypeScript ( Se puede configurar al gusto)
chrome.action.onClicked.addListener((tab) => { | |
chrome.scripting.executeScript({ | |
target: { | |
tabId: tab.id, | |
}, | |
files: ["content.js"], | |
}); | |
}); |
Más información - Docs Oficiales
npm i -D typescript @types/node
<?php | |
function custom_search($search, $wp_query) { | |
global $wpdb; | |
//サーチページ以外だったら終了 | |
if (!$wp_query->is_search) | |
return $search; | |
if (!isset($wp_query->query_vars)) | |
return $search; |
I liked the way Grokking the coding interview organized problems into learnable patterns. However, the course is expensive and the majority of the time the problems are copy-pasted from leetcode. As the explanations on leetcode are usually just as good, the course really boils down to being a glorified curated list of leetcode problems.
So below I made a list of leetcode problems that are as close to grokking problems as possible.
This is me documenting my journey moving my Homelab from a Qnap NAS and a Single host Proxmox server to a Hyper-converged multi-node Proxmox Cluster.
The reason to document it here is twofold:
It's written 'first to scratch my own itch' but hopefully it benefits others too, or even better, that others improve upon my implementations. Feel free to comment or share improvements and insights!
Part of collection: Hyper-converged Homelab with Proxmox
Keepalived is a Loadbalancer to add ‘high availability` to Linux systemen. See the Keepalived documentatie for more background information.
This setup build on High Available Pi-hole failover cluster using Keepalived and Orbital Sync.
Part of collection: Hyper-converged Homelab with Proxmox
After struggling for some days, and since I really needed this to work (ignoring the it can't be done vibe everywhere), I managed to get Docker to work reliable in privileged Debian 12 LXC Containers on Proxmox 8
(Unfortunately, I couldn't get anything to work in unprivileged LXC Containers)
There are NO modifications required on the Proxmox host or the /etc/pve/lxc/xxx.conf
file; everything is done on the Docker Swarm host. So the only obvious candidate who could break this setup, are future Docker Engine updates!
L1 cache reference ......................... 0.5 ns
Branch mispredict ............................ 5 ns
L2 cache reference ........................... 7 ns
Mutex lock/unlock ........................... 25 ns
Main memory reference ...................... 100 ns
Compress 1K bytes with Zippy ............. 3,000 ns = 3 µs
Send 2K bytes over 1 Gbps network ....... 20,000 ns = 20 µs
SSD random read ........................ 150,000 ns = 150 µs
Read 1 MB sequentially from memory ..... 250,000 ns = 250 µs
From self[at]sungpae.com Mon Nov 8 16:59:48 2021 | |
Date: Mon, 8 Nov 2021 16:59:48 -0600 | |
From: Sung Pae <self[at]sungpae.com> | |
To: security@docker.com | |
Subject: Permissive forwarding rule leads to unintentional exposure of | |
containers to external hosts | |
Message-ID: <YYmr4l1isfH9VQCn@SHANGRILA> | |
MIME-Version: 1.0 | |
Content-Type: multipart/signed; micalg=pgp-sha256; | |
protocol="application/pgp-signature"; boundary="QR1yLfEBO/zgxYVA" |
qApp.setStyle("Fusion") | |
dark_palette = QPalette() | |
dark_palette.setColor(QPalette.Window, QColor(53, 53, 53)) | |
dark_palette.setColor(QPalette.WindowText, Qt.white) | |
dark_palette.setColor(QPalette.Base, QColor(25, 25, 25)) | |
dark_palette.setColor(QPalette.AlternateBase, QColor(53, 53, 53)) | |
dark_palette.setColor(QPalette.ToolTipBase, Qt.white) | |
dark_palette.setColor(QPalette.ToolTipText, Qt.white) |