Scott Anderson sanderson

It goes without saying – security is of the utmost importance in your production infrastructure. Nanobox was built with strict security protocols in place. The following measures have been put in place to reduce your app's attack plane.

The Initial Bootstrap

Each and every server provisioned through Nanobox uses a simple Ubuntu bootstrap script (feel free to view the source). This bootstrap installs and configures Docker and the Nanobox agent as well as a brutal, default-deny firewall via iptables and a custom overlay network. It also ensures that the core software is up-to-date.

Once a host is bootstrapped, you essentially have a machine that is fully locked-down, running only Docker, the Nanobox agent, and the virtual network. At this point, not even the other machines within the same network can talk to the machine.

Updates via the Dashboard

After the initial bootst

Hugo Project Bootstrap with Nanobox

If you haven't already, go ahead and download and install Nanobox.

# Create a new directory for your project and cd in
mkdir hugo-proj && cd hugo-proj

# Create a `boxfile.yml` using the content from this gist
curl -sL http://tinyurl.com/ya23f5ry &gt; boxfile.yml

Moving from Nanobox v1 to v2

Nanobox v2 is here and provides some significant advantages when compared to v1 (most notable is support for native Docker containers). There have been changes to the Nanobox core that require a fresh install.

Uninstall Nanobox v1

If you have local data you want to preserve, you should export it before unistalling

Use the nanobox implode command to destroy all your v1 apps.
Remove/Uninstall the Nanobox binaries - nanobox and nanobox-update. (Windows users, do this through the system uninstaller)
If you've been using netfs for filesystem mounting, remove the Nanobox entries in your /ect/exports files.

	run.config:
	engine: php
	engine.config:
	runtime: php-7.0
	document_root: public
	webserver: apache
	extensions:
	- ctype
	- pdo
	- pdo_mysql

	8950 4e47 0d0a 1a0a 0000 000d 4948 4452
	0000 006f 0000 006f 0806 0000 00e2 c59e
	6000 000b 3d49 4441 5478 9ced 9dcf 6be3
	661a c7df 6c8b 9121 2656 0c03 3234 7234
	8c87 4aa6 3116 4b13 6c6a 977a 6006 12aa
	43cd 6e0f d3f1 cca1 bb7b f37f 50f7 b47b
	746f 4b0b 3b9e 9943 0f2e acc3 4cd9 8171
	97b8 d80c 3dd8 78c0 d696 049c 084a 5418
	1cdb c410 6132 b007 e59d 98d8 b225 5992
	e5e4 fd1c 9d58 92df af9e f77d de1f cff3

	// Upper and Lower Ends
	$sm-upper: "(max-width: 40em)"; /* 640px */
	$md-lower: "(min-width: 40.063em)"; /* 641px */
	$md-upper: "(max-width: 54em)"; /* 864px */
	$lg-lower: "(min-width: 54.063em)"; /* 865px */
	$lg-upper: "(max-width: 90em)"; /* 1440px */

	// Specifications
	$screen: only screen !default;

	#!/bin/bash

	# Exits script on error
	set -e

	# Export a backup from db1 into writable storage
	mysqldump -h $DB1_HOST -P $DB1_PORT $DB1_NAME -u $DB1_USER -p$DB1_PASS > path/to/writable_dir/data_migration.sql

	# Import the backup into db2
	mysql -h $DB2_HOST -P $DB2_PORT -u $DB2_USER -p$DB2_PASS $DB2_NAME < path/to/writable_dir/data_migration.sql

	web1:
	document_root: public
	php_version: 5.3.10
	php_extensions:
	- mbstring
	- mcrypt
	- pdo_mysql
	- mysql
	- apc
	- memcached

	web1:
	apache_access_log: false
	apache_error_log: true
	php_error_log: true
	php_fpm_log: true