Skip to content

Instantly share code, notes, and snippets.

Tyler Flint tylerflint

View GitHub Profile
@tylerflint
tylerflint / boxfile.yml
Created Dec 27, 2016
Hugo with nanobox
View boxfile.yml
run.config:
engine: static
cache_dirs:
- .bin
extra_path_dirs:
- /app/.bin
extra_steps:
@tylerflint
tylerflint / resize_nanobox_vm.sh
Last active Dec 6, 2016 — forked from joost/resize_boot2docker.sh
Resize Nanobox VirtualBox image
View resize_nanobox_vm.sh
# Steps we will take:
# 1. Change virtualbox image type (this will take a bit)
# 2. Resize image
# 3. Resize partion (using GParted)
#
# Stop nanobox
nanobox stop
# First we need to change the size of the image.
@tylerflint
tylerflint / README.md
Last active Nov 21, 2016
Nanobox run & deploy
View README.md

Major changes

We have been working on some exciting changes! This is a fundamental shift in workflow, in how nanobox is used, and how nanobox works for you. After about a dozen conversations that all followed the same pattern, it occurred to us: Nanobox needs to be simpler, it needs to get out of the way. And that's exactly what we did, we threw away the clunky workflow and started over.

Overview

Excluding one-time-only administrative commands like adding evars, Nanobox has been stripped down to two primary commands:

nanobox run
@tylerflint
tylerflint / reset-lines.sh
Created Oct 13, 2016
Test line reset on *nix
View reset-lines.sh
#!/bin/bash
echo "+ Building application : "
echo " √ Pulling latest docker image "
echo " √ Starting docker container "
echo " √ Preparing environment for build "
echo " √ Installing binaries and runtimes "
echo "hey"
echo "there"
@tylerflint
tylerflint / 1-boxfile.yml
Created Sep 30, 2016
Add nodejs support into nanobox app config
View 1-boxfile.yml
code.build:
engine: ruby
@tylerflint
tylerflint / output1.txt
Last active May 10, 2016
nanobox build hooks output
View output1.txt
+> Copying user's ssh keys into the build environment
+> Setting up directories and permissions
+> Cleaning up any previous builds
UPDATING PKG DATABASE ----------------->
reading local summary...
processing local summary...
updating database: 100%
pkg_summary.bz2 100% 159KB 159.1KB/s 40.1KB/s 00:01
processing remote summary (http://pkgsrc.nanobox.io/nanobox/base/Linux/)...
@tylerflint
tylerflint / .htaccess
Created Jan 28, 2016
Apache .htaccess configuration for disabling browser to cache files
View .htaccess
Header unset ETag
Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate"
Header set Pragma "no-cache"
Header set Expires "Wed, 11 Jan 1984 05:00:00 GMT"
@tylerflint
tylerflint / Boxfile
Created Nov 24, 2015
example rails Boxfile
View Boxfile
build:
webserver: puma
web1:
name: web
worker1:
name: workerz
redis1:
@tylerflint
tylerflint / database.yml
Created Nov 24, 2015
configure rails database for nanobox
View database.yml
development:
adapter: postgresql
encoding: unicode
database: <%= ENV['POSTGRESQL1_NAME'] %>_development
pool: 25
host: <%= ENV['POSTGRESQL1_HOST'] %>
username: <%= ENV['POSTGRESQL1_USER'] %>
password: <%= ENV['POSTGRESQL1_PASS'] %>
test:
@tylerflint
tylerflint / questions.md
Created Nov 19, 2015
Engine find out questions
View questions.md

A nanobox engine is responsible for 5 things:

  1. Determining if the app type matches the engine
  2. Detecting service dependencies like postgres, redis, etc
  3. Preparing the environment that the application (code) will run within.
  4. Configuring the application to connect to the detected services.
  5. Compiling or building the code into a release.

We would greatly appreciate it if you would be willing to answer some or all of the following questions, in as much detail as you need, understanding that there are no wrong answers:

You can’t perform that action at this time.