adamreisnz

{
  "name": "project-name",
  "description": "Template for static sites",
  "version": "1.0.0",
  "homepage": "http://www.project-name.com",
  "author": {
    "name": "Adam Reis",
    "url": "http://adam.reis.nz"
  },
  "license": "UNLICENSED",

jbanety

# Brew Formulas
brew update
brew install libpng jpeg lzlib freetype readline openssl imap-uw curl postgresql libxml2 gettext libxslt mcrypt homebrew/dupes/libiconv icu4c expat

# MAMP
mkdir -p /Applications/MAMP/bin/php/php7.0.6/include
cd /Applications/MAMP/bin/php/php7.0.6/include

# Download PHP
wget -O php-7.0.6.tar.bz2 http://fr2.php.net/get/php-7.0.6.tar.bz2/from/this/mirror

nukeador

This guide provides detailed steps for setting up DNS records, configuring a DNS tunneling server and client, and setting up a browser for secure proxy connections.

Why iodine?

• Bypassing Network Restrictions: iodine excels in environments with strict network restrictions. It utilizes DNS queries, which are typically allowed through firewalls, to tunnel data where traditional methods like VPNs might be blocked.
• Efficient for Limited Bandwidth: Ideal for situations with bandwidth limitations, iodine requires less bandwidth compared to standard VPNs, making it a practical choice for networks with restricted data flow.
• Customizability and Open Source: As an open-source tool, iodine offers extensive customization options. Users with specific technical needs or those interested in a hands-on approach to network tunneling can tailor iodine to their requirements.

Prerequisites