Static Sites Powered By Nuxt and AWS
Tags: nuxt, aws, staticsites, showdev
Published: 2018-08-20 18:42:32

---
title: Static Sites Powered By Nuxt and AWS
published: true
description: In which I detail how I built my new personal blog using Nuxt and deployment to AWS S3
tags: nuxtjs, aws, staticsites, showdev
---

This post was originally published on my [blog](https://leesmith.net/posts/static-sites-powered-by-nuxt-and-aws).

![Nuxt and AWS](https://thepracticaldev.s3.amazonaws.com/i/rd5n1lbv0ww72ht01r90.png "Static Sites Powered By Nuxt and AWS")

I'd like to share how I built my new [personal site and blog](https://leesmith.net/). My goals were pretty simple as far as a static blog. Obviously, I didn't want to use a CMS. I wanted to use a static hosting environment so I didn't have to manage a server. I also wanted to explore technologies aimed at the front-end since I spend a lot of my time building web applications using server-side languages. There's really a lot going on right now in the static site generation space. Static sites have certainly proven their value, especially when it comes to performance and cost factors. From the React community, Next.js and Gatsby have taken off in popularity. Hugo is a popular project written in Go and VuePress came alive just this past April.

So I ended up choosing [Nuxt](https://nuxtjs.org/) as my static site generator. Nuxt is a high level framework that sits on top of Vue and offers many cool features and also some conventions that I appreciate. I've been keeping my eye on Vue for a while and I like what I see so that also played a part in my choosing Nuxt. I'm also deploying to AWS S3 and using AWS Cloudfront as a CDN for better performance and HTTPS communication. This site is open source so feel free to check it out on [Github](https://github.com/leesmith/leesmith-dot-net).

## Nuxt

 Nuxt, primarily inspired by Next.js, is a high level framework for developing universal JavaScript applications in Vue. By default, Nuxt supports server-side rendering but can also be configured as a SPA. The big innovation of Nuxt is "pre rendering" which allows you to generate your web app so that it can be hosted on any of the popular static hosting providers like Amazon S3 or Netlify.

Starting out, I used the following commands to create my project: 

    # install vue-cli globally
    npm install -g vue-cli

    # create a project using a nuxt template
    vue init nuxt-community/starter-template leesmith-dot-net

    # cd into the project and install dependencies
    cd leesmith-dot-net
    npm install

    # spin up a local dev server on port 3000
    npm run dev

At this point, Nuxt has created a basic project structure including `assets`, `components`, `layouts`, `pages`, and `plugins` among others. With my site, I've built a basic layout and each post I make simply sits inside my layout. One of the conventions that you get with Nuxt is that each `.vue` component file you place in the pages directory gets generated into its own html file. Inside of my pages directory, I have a posts directory that contains each blog post of my site. With this convention, there's very little configuring to do on your part.

The `nuxt.config.js` file defines project-wide settings. There is a section that allows you to set the attributes for the elements in the `<head>` section. You'll want to set things like language and meta tags among other things.

As far as a layout, the following would suffice for something very basic:

    <template>
      <header>
        <h1>Example Site Title</h1>
      </header>
      <section>
        <nuxt/>
      </section>
    </template>

    <script>
    </script>

    <style>
    </style>

The following would suffice for a basic page:

    <template>
      <article><p>Hello World</p></article>
    </template>

    <script>
    </script>

    <style>
    </style>

One of my favorite features you get out of the box are page transitions, which are powered by Vue. It gives the site a native feel instead of the usual "blink" when clicking around to different pages. To control the styling of page transitions, you need to add styles for the transition hooks, like so:

    .page-enter-active,
    .page-leave-active {
      transition: opacity 0.3s;
    }

    .page-enter,
    .page-leave-to {
      opacity: 0;
    }

I've chosen Bulma as my CSS framework. I'm also using Fontawesome icons as well as vue-highlightjs plugins. I'll probably write some future posts detailing these further.

In addition to the project-wide settings in `nuxt.config.js`, you can control meta tags at the page level. I want each blog post (page) to have a custom title. To do this, you can tap into Nuxt's API - specifically the `head()` method:

    // script section of your vue component
    <script>
    export default {
      head() {
        return {
          title: "Static sites powered by Nuxt and AWS - LeeSmith.net",
          meta: [
            {
              hid: "description",
              name: "description",
              content: "Static sites powered by Nuxt and AWS"
            }
          ]
        };
      }
    };
    </script>

So those are some of the basics as far as Nuxt. From here you could generate your site:

    npm run generate

Nuxt produces a `dist` folder containing your generated site files. These are the files you'd push to your static host. Let's see how that works when hosting with Amazon.

## AWS Setup

Getting set up on AWS is pretty straight forward. They have easy to follow documentation for the entire process. I won't recreate their documentation here but the first thing you'll do is create your S3 bucket and enable static hosting on it. I'm assuming you've already registered a domain name but if you haven't, I recommend using AWS Route 53 for domain registration and DNS management.

Follow the [AWS S3 walkthrough](https://docs.aws.amazon.com/AmazonS3/latest/dev/HostingWebsiteOnS3Setup.html) for creating and configuring your S3 bucket.

At this point, you could push up your generated site files to make sure your bucket is configured properly. I highly recommend using the [awscli](https://aws.amazon.com/cli/) when working with AWS. Pointing and clicking through the web console isn't the most efficient way to get things done. Once awscli is installed and configured for your AWS account, you should be able to copy your files to your bucket:

    aws s3 cp dist s3://mybucket --recursive

Now that the S3 bucket is serving your site, the next thing you would do is serve your website through an AWS Cloudfront distribution. This allows you to improve performance by making your website's static files (such as HTML, images, and video) available from data centers around the world (which they call edge locations). With AWS Cloudfront you can also configure your website to be served over HTTPS. Speed and security are vital for today's web. HTTPS for websites is pretty much the standard as [browsers will now warn you](https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html) when pages are not using HTTPS. Google search algorithms also [favor faster websites](https://developers.google.com/web/updates/2018/07/search-ads-speed).

Follow the [AWS Cloudfront walkthrough](https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-cloudfront-walkthrough.html) for creating and configuring your Cloudfront distribution.

So far, lighthouse scores look pretty good:

![Lighthouse](https://thepracticaldev.s3.amazonaws.com/i/5sgnln5pa14tozy5u0jb.png "Lighthouse score")

## Deployment

I've put together a simple script to automate deployment. This script depends on your AWS settings. It creates a `.env` file if one does not exist and after you fill in the two variables (S3 URI and Cloudfront distribution ID), deployment is as simple as running the script. I'm using the S3 `sync` command to push my files to the bucket. The `sync` command is using a cache-control option to set a far future max-age value for the files as well as a delete option that will delete anything in the bucket that's not contained in my dist directory. In addition to sync'ing the files to the bucket, we also need to invalidate our cloudfront distribution so that future visits to the site get served the latest content.

    # deploy.sh
    if [ ! -f .env ]; then
        echo "# Project environment variables...do not commit this file." >> .env
        echo "AWS_CF_DIST_ID=" >> .env
        echo "AWS_S3_URI=" >> .env
        echo "Please add the necessary values to the .env file."
    else
        export $(egrep -v '^#' .env | xargs)
        echo "CF DIST -> $AWS_CF_DIST_ID"
        echo "S3 URI -> $AWS_S3_URI"
        echo "Performing sync..."
        aws s3 sync dist s3://$AWS_S3_URI --cache-control "max-age=31536000" --delete
        echo "Invalidating cloudfront distribution..."
        aws cloudfront create-invalidation --distribution-id $AWS_CF_DIST_ID --paths "/*"
        echo "Deploy complete! 🎉"
    fi

You could automate your deploys even further by using a CI/CD service like [Semaphore](https://semaphoreci.com/docs/deploying-to-amazon-s3.html) so that each push to your master branch kicks off a deploy. This is very similar to what Netlify offers. I could see that being a nice feature when working on a larger project.

So far, I've really enjoyed playing around with Nuxt. Hit me up on [Twitter](https://twitter.com/jeremyleesmith) with any questions/comments.

Cheers! 🍻