I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables.
What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding.
Here’s how it’s done:
UPDATED: 2025-04-04
| echo "" | |
| echo "************ Github Dork Links (must be logged in) *******************" | |
| echo "" | |
| echo " password" | |
| echo "https://github.com/search?q=%22$1%22+password&type=Code" | |
| echo "https://github.com/search?q=%22$without_suffix%22+password&type=Code" | |
| echo "" | |
| echo " npmrc _auth" |
DigitalOcean does not provide a way to download a snapshot of your droplet locally. You can use rsync to accomplish this instead.
On your local machine, assuming you have added your-server in your SSH config:
rsync -aAXHv --append-verify --exclude={"/dev/*","/proc/*","/sys/*","/tmp/*","/run/*","/mnt/*","/media/*","/lost+found"} your-server:/
-a : archive mode (all files, with permissions, etc.)-A : preserve ACLs/permissions (not included with -a)
| <?php | |
| // Safely Remove CPT slugs from your CPT permalinks. | |
| // Note: Replace CPT_NAME with your CPT name. | |
| /** | |
| * Remove the slug from published post permalinks. Only affect our custom post type, though. | |
| */ | |
| function m3_remove_cpt_slug( $post_link, $post ) { | |
| if ( 'CPT_NAME' === $post->post_type && 'publish' === $post->post_status ) { |
A step-by-step guide for running a headless Raspbian 64bit kernel and OS on Raspberry Pi. The provided configuration has been tested on models 3B, 3B+ and 4B.
Download the Raspberry Pi Imager application.
Use the application to download Raspbian Lite (under Raspbian (other)) and write the image on your SD card.
Setup wireless connection configuration by creating wpa_supplicant.conf file in the boot folder:
Convert mac-os-el-capitan-pkg-to-iso.sh from using hdiutil and asr to using Linux utilities.
Important: You will need about 30GB of free disk space.
| echo "" | |
| echo "************ Github Dork Links (must be logged in) *******************" | |
| echo "" | |
| echo " password" | |
| echo "https://github.com/search?q=%22$1%22+password&type=Code" | |
| echo "https://github.com/search?q=%22$without_suffix%22+password&type=Code" | |
| echo "" | |
| echo " npmrc _auth" |
Follow these steps to install Proxmox VE on a Hetzner server via the Rescue System. The Rescue System is a Linux-based environment that can be booted into to perform system recovery tasks. We'll be using it to install Proxmox VE.
In order to complete the process, it is indeed necessary to first boot into the Rescue System and then connect to it via SSH. This will allow you to run the commands for installing Proxmox VE. Here are the steps:
