hugo/content/hosting-and-deployment/deployment-with-nanobox.md
Bjørn Erik Pedersen 337d0c5f51 Squashed 'docs/' changes from 56c34962c..dce236ad1
dce236ad1 Wrap up the bundle etc. edits for now
27d058566 Add the bundle tree to the organization bundle
a83f750dd Move organization.md to its own bundle
01ec4f462 Make the image docs a bundle
60de1e090 Some more resources copy-edits
05d763c0c Some resource copy-edits
6299d6dbb Update the imgproc shortcode
59e0fc209 Add headless bundle documentation
a3bbf60bf Link Page Resources page from Front Matter page
830576f86 Update order significance section, add counter section
3b1836509 Revert the recent change made to default list template
886ed0e10 Page Bundles draft rev 2
f530d1a7a image processing and page resources made into regular .md
ec47cecda Finalised Page Resources and Image Processing Moved Page Resources and Impage Processing out of the Bundle section and at the root of the Content Management section
253092335 Modified front matter metadata exemple. Added yaml version.
da5e4f476 Adding date in the front-matter; missed in previous commit
6bc3ced13 Add rough draft for page and section bundles
a0e44458f Image processing first draft, Resources second read/fix
2367f0b78 data: Remove duplicate layouts in table
c2f179839 First draft of bundles/resources (covers resources and metadata)
2a3f9a613 Add weights to pages in Bundles branch
9a0146cc0 Switch front-matter format of Bundles doc to yaml; add front-matter
1295fc083 First draft for Bundles documentation organization structure
5a2e52231 Fix archetype paths
9c2e5c063 Merge commit '22cced34fc608256f8271ad591a5ccca991bb164'
22cced34f Squashed 'themes/gohugoioTheme/' changes from 75da2f6b..ecad8247
55d16c9a1 Fix broken sentence in multilingual sections
a76895ad2 Replace the outdated Emacs package with new one
e6cf1dec0 Remove obsolete link to hugo roadmap
dd2fd145b Add GitLab Pages to mentioned hosters (#309)
a05ce6bf6 Add 0.34 release notes poster
5c0ebdfca Release 0.34
13c2f3dc8 Merge branch 'temp34'
e6b5ffa04 Add 0.34 poster
1e1960496 releaser: Add release notes to /docs for release of 0.34
ac3efe182 releaser: Bump versions for release of 0.34
8f91f62d8 Fixes #222
cca35dbe4 Fix example
eaaa21ca1 Add missing params key
00d0b0363 Adding new Blogger utility to tools/migrations
7d36d579e Updated the line number for Dockerfile pointer
852188f85 Update installing.md with Fedora instructions
4d151a3ab Update search.md
4c2750bfb Update deployment-with-nanobox.md
c3cc9cd49 configuration: Remove defaultExtension from docs
f7c96b4b5 Update GitHub Pages documentation
55787f09a Merge branch 'rmetzler-menu-link-title'
2abbd9bd9 Merge branch 'master' into menu-link-title
e1fd710b7 Bring archetypes in from theme.
daf6f51c0 Mention the significance of leading 0 in int fn string input
07f498755 Add documentation for `cond` function.
050ccd12b Add documentation for the .HasShortcode function
919af9071 Correct anchor under 'Add custom metadata to a Taxonomy Term'
55600b4ff More layouts work
201cf4f67 Add some more single page layout variants
d5e7c03e2 Rework the layouts doc
84622e67c Cleans up the code sample
c231c9bd5 Add a new note to 0.33 relnotes
328ec9930 Release 0.33
b108fcc7b Merge branch 'temp33' into next
ab9d9ee65 releaser: Prepare repository for 0.34-DEV
e20c75320 releaser: Add release notes to /docs for release of 0.33
49f24dcd1 releaser: Bump versions for release of 0.33
9c8e5e207 Update 0.33 poster
7655603c8 Regenerate the docshelper data
16dc99583 Add Hugo 0.33 poster
ce40cc197 Merge commit '3cf4300097610bb8b5bd0686d96d1df5db641895'
9a3085523 releaser: Prepare repository for 0.33-DEV
a52db97d8 fixing typos and syntax for consistency
64525670f ádd title to some menu entries. This needs hugo >= v0.32
85d415ab2 ádd examples for menu .Title and .Page

git-subtree-dir: docs
git-subtree-split: dce236ad1258a9d9a0ee209f02b2e1f65b46f0fb
2018-01-31 11:07:47 +01:00

8.5 KiB

title linktitle description date publishdate lastmod categories keywords authors menu weight sections_weight draft aliases toc
Host-Agnostic Deploys with Nanobox Host-Agnostic Deploys with Nanobox Easily deploy Hugo to AWS, DigitalOcean, Google, Azure, and more... 2017-08-24 2017-08-24 2017-08-24
hosting and deployment
nanobox
deployment
hosting
aws
digitalocean
azure
google
linode
Steve Domino
docs
parent weight
hosting-and-deployment 05
05 05 false
/tutorials/deployment-with-nanobox/
true

hugo with nanobox

Nanobox provides an entire end-to-end workflow for developing and deploying applications. Using Nanobox to deploy also means you'll use it to develop your application.

{{% note %}} If you're already using Nanobox and just need deployment instructions, you can skip to Deploying Hugo with Nanobox {{% /note %}}

What You'll Need

With Nanobox you don't need to worry about having Golang or Hugo installed. They'll be installed as part of the development environment created for you.

To get started you'll just need the following three items:

Before You Begin

There are a few things to get out of the way before diving into the guide. To deploy, you'll need to make sure you have connected a host account to your Nanobox account, and launched a new application.

Connect a Host Account

Nanobox lets you choose where to host your application (AWS, DigitalOcean, Google, Azure, etc.). In the Hosting Accounts section of your Nanobox dashboard link your Nanobox account with your host.

Launch a New Application on Nanobox

Launching a new app on Nanobox is very simple. Navigate to Launch New App in the dashboard, and follow the steps there. You'll be asked to name your app, and to select a host and region.

With those out of the way you're ready to get started!

Getting Started

{{% note %}} If you already have a functioning Hugo app, you can skip to Configure Hugo to run with Nanobox {{% /note %}}

To get started, all you'll need is an empty project directory. Create a directory wherever you want your application to live and cd into it:

mkdir path/to/project && cd path/to/project

Configure Hugo to run with Nanobox

Nanobox uses a simple config file known as a boxfile.yml to describe your application's infrastructure. In the root of your project add the following boxfile.yml:

{{< code file="boxfile.yml" >}} run.config:

use the static engine

engine: static engine.config:

# tell the engine where to serve static assets from
rel_dir: public

enable file watching for live reload

fs_watch: true

install hugo

extra_steps: - bash ./install.sh

deploy.config:

generate site on deploy

extra_steps: - hugo

{{< /code >}}

{{% note %}} If you already have a functioning Hugo app, after adding the boxfile, you can skip to Deploying Hugo with Nanobox. {{% /note %}}

Installing Hugo

Nanobox uses Docker to create instant, isolated, development environments. Because of this, you'll need to make sure that during development you have Hugo available.

Do this by adding a custom install script at the root of your project that will install Hugo automatically for you:

{{< code file="install.sh" >}}

#!/bin/bash

if ! -f /data/bin/hugo ; then cd /tmp wget https://github.com/gohugoio/hugo/releases/download/v0.31.1/hugo_0.31.1_Linux-64bit.tar.gz tar -xzf hugo_0.31.1_Linux-64bit.tar.gz mv hugo /data/bin/hugo cd - rm -rf /tmp/* fi

{{< /code >}}

{{% note %}} If the install script fails during nanobox run you may need to make it executable with chmod +x install.sh {{% /note %}} {{% note %}} Make sure to check the version of Hugo you have installed and update the install script to match. {{% /note %}}

Generating a New Hugo App

You'll generate your new application from inside the Nanobox VM (this is why you don't need to worry about having Golang or Hugo installed).

Run the following command to drop into a Nanobox console (inside the VM) where your codebase is mounted:

nanobox run

nanobox run

Once inside the console use the following steps to create a new Hugo application:

# cd into the /tmp dir to create an app
cd /tmp

# generate the hugo app
hugo new site app

# cd back into the /app dir
cd -

# copy the generated app into the project
shopt -s dotglob
cp -a /tmp/app/* .

Install a theme

cd into the themes directory and clone the nanobox-hugo-theme repo:

cd themes
git clone https://github.com/sdomino/nanobox-hugo-theme

To use the theme either copy the entire config.toml that comes with the theme, or just add the theme to your existing config.toml

# copy the config.toml that comes with the theme
cp ./themes/nanobox-hugo-theme/config.toml config.toml

# or, add it to your existing config.toml
theme = "nanobox-hugo-theme"

{{% note %}} It is not intended that you use the nanobox-hugo-theme as your actual theme. It's simply a theme to start with and should be replaced. {{% /note %}}

View Your App

To view your application simply run the following command from a Nanobox console:

hugo server --bind="0.0.0.0" --baseUrl=$APP_IP

hugo server

With that you should be able to visit your app at the given IP:1313 address

{{% note %}} You can add a custom DNS alias to make it easier to access your app. Run nanobox dns add local hugo.dev. After starting your server, visit your app at hugo.dev:1313 {{% /note %}}

Develop, Develop, Develop

{{% note %}} IMPORTANT: One issue we are aware of, and actively investigating, is livereload. Currently, livereload does not work when developing Hugo applications with Nanobox. {{% /note %}}

With Hugo installed you're ready to go. Develop Hugo like you would normally (using all the generators, etc.). Once your app is ready to deploy, run hugo to generate your static assets and get ready to deploy!

Deploying Hugo with Nanobox

{{% note %}} If you haven't already, make sure to connect a hosting account to your Nanobox account, and launch a new application in the Dashboard. {{% /note %}}

To deploy your application to Nanobox you simply need to link your local codebase to an application you've created on Nanobox. That is done with the following command:

nanobox remote add <your-app-name>

{{% note %}} You may be prompted to login using your Nanobox credentials at this time {{% /note %}}

Stage Your Application (optional)

Nanobox gives you the ability to simulate your production environment locally. While staging is optional it's always recommended, so there's no reason not to!

To stage your app simply run:

nanobox deploy dry-run

Now visit your application with the IP address provided.

nanobox deploy dry-run

Deploy Your Application

Once everything checks out and you're ready to deploy, simply run:

nanobox deploy

Within minutes you're Hugo app will be deployed to your host and humming along smoothly. That's it!