| -- vim: tabstop=2 shiftwidth=2 expandtab | |
| -- We almost always start by importing the wezterm module | |
| local wezterm = require 'wezterm' | |
| -- Define a lua table to hold _our_ module's functions | |
| local module = {} | |
| -- Returns a bool based on whether the host operating system's | |
| -- appearance is light or dark. | |
| function module.is_dark() |
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
| #!/bin/env bash | |
| cheat='curl -s cheat.sh' | |
| menu='fzf --reverse' | |
| pager='less -R -c' | |
| cachefile_max_age_hours=6 | |
| # Path to temporary cache file. If your Linux system does not support /dev/shm | |
| # or if you are on MacOS, then change the path to your liking: | |
| cachefile='/dev/shm/cheatlist' # GNU+LINUX |
| from io import StringIO | |
| from django.core.management import call_command | |
| from django.test import TestCase | |
| class PendingMigrationsTests(TestCase): | |
| def test_no_pending_migrations(self): | |
| out = StringIO() | |
| try: | |
| call_command( |
I have a Linux virtual machine inside a customer's private network. For security, this VM is reachable only via VPN + Citrix + Windows + a Windows SSH client (eg PuTTY). I am tasked to ensure this Citrix design is secure, and users can not access their Linux VM's or other resources on the internal private network in any way outside of using Citrix.
The VM can access the internet. This task should be easy. The VM's internet gateway allows it to connect anywhere on the internet to TCP ports 80, 443, and 8090 only. Connecting to an internet bastion box on one of these ports works and I can send and receive clear text data using netcat. I plan to use good old SSH, listening on tcp/8090 on the bastion, with a reverse port forward configured to expose sshd on the VM to the public, to show their Citrix gateway can be circumvented.
I hit an immediate snag. The moment I try to establish an SSH or SSL connection over o
| LOGGING = { | |
| "version": 1, | |
| "disable_existing_loggers": False, | |
| "filters": { | |
| "require_debug_true": { | |
| "()": "django.utils.log.RequireDebugTrue", | |
| }, | |
| }, | |
| "formatters": { | |
| "rich": {"datefmt": "[%X]"}, |
| # Full NixOS configuration for a ZFS server with full disk encryption hosted on Hetzner. | |
| # See <https://mazzo.li/posts/hetzner-zfs.html> for more information. | |
| { config, pkgs, ... }: | |
| let | |
| # Deployment-specific parameters -- you need to fill these in where the ... are | |
| hostName = "..."; | |
| publicKey = "..."; | |
| # From `ls -lh /dev/disk/by-id` |
First of all, make sure to refer and understand the general instructions in the official NocoDB site:
https://docs.nocodb.com/getting-started/installation
What you'll find here are the specific instructions to setup NocoDB in a FreeBSD system, or in a FreeNAS/TrueNAS CORE jail.
This was originally done in a TrueNAS CORE 12.0-U5.1, which uses FreeBSD 12.4-RELEASE-p6 as base system.
Instructions to obtain WireGuard details of your NordVPN account. These can be used to setup a WireGuard tunnel on your router to NordVPN.
Source: https://forum.gl-inet.com/t/configure-wireguard-client-to-connect-to-nordvpn-servers/10422/27
If you have any linux machine, use that or install a vm if you don't have one.
Get their official linux app installed. Make sure you have wireguard installed too. And set the used technology to Nordlynx by running nordvpn set technology nordlynx
All packages, except for Tini have been added to termux-root. To install them, simply pkg install root-repo && pkg install docker. This will install the whole docker suite, left only Tini to be compiled manually.
