https://github.com/kconner/next-js-in-docker-example

Next.js + Docker + Compose + Kubernetes + VS Code + TypeScript + Jest + Storybook
https://github.com/kconner/next-js-in-docker-example

Last synced: 4 months ago
JSON representation

Next.js + Docker + Compose + Kubernetes + VS Code + TypeScript + Jest + Storybook

• Host: GitHub
• URL: https://github.com/kconner/next-js-in-docker-example
• Owner: kconner
• Created: 2019-09-10T00:23:37.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2022-06-25T04:47:25.000Z (over 2 years ago)
• Last Synced: 2024-04-14T06:51:50.639Z (7 months ago)
• Language: Shell
• Homepage:
• Size: 185 KB
• Stars: 100
• Watchers: 6
• Forks: 23
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Next.js in Docker Example

This repository demonstrates a Next.js web application that uses Docker for both deployment and a development environment.

Check my commit messages to see the tutorial articles and documentation I followed as I built this up piece by piece.

## Progress

- [x] Node app in Docker

- [x] Debuggable in VS Code

- [x] Development and Release container variants

- [x] Next.js

- [x] TypeScript

- [x] Allow launching Storybook at the test stage

- [x] Allow running CI tools at the test stage

- [x] Allow debugging individual tests

- [x] Use multi-stage Docker builds for compact release artifacts

- [x] Use layer caching for efficient builds

- [x] Deploy to Kubernetes with kubectl

- [x] Demonstrate a complete CI workflow

- [x] Allow running CI tools against a built release artifact to validate it

- [ ] Deploy with Helm instead of kubectl

## How this setup uses Docker

- `Dockerfile` describes a multi-stage build.

    - The test stage includes a copy of the checked out workspace with all packages installed. The builds for the CI and debug services stop here.

    - The build stage continues by removing development packages and preparing a release build.

    - The archive stage starts fresh and copies in just what's needed at runtime for a small release container.

- `docker-compose.yml` prepares a development environment including a debuggable web server and a Storybook server.

- `scripts/run-continuous-integration.sh` and its helper scripts perform a complete CI workflow, including building the application in Docker containers, testing it, pushing it to a container registry, and deploying it to Kubernetes.

## How to use this setup

- Clone the repo.

- Install Docker and VS Code.

- Open `app.code-workspace`. VS Code will recommend a Docker plugin if you don't have it, so install that.

- To develop in Docker, right-click `docker-compose.yml` and select Compose Up.

    - Canonically, `docker-compose up` will start debug mode too. Add `--build` if you have made changes since last time.

    - In VS Code's activity bar, click the Docker icon to view running containers.

    - Visit localhost:3000 to view the site.

    - Visit localhost:6006 to view Storybook. It may take a moment for the Storybook server to start after docker-compose launches its container.

    - Save a code file to hot-reload the browser.

    - Select Start Debugging from the Debug menu to attach the debugger. Then click in VS Code's gutter to set breakpoints. In this example, only the web server is debuggable, not Storybook.

    - To stop, right-click again and select Compose Down, or use `docker-compose down`.

- In addition to the Docker debugger attachment launcher, VS Code launchers also exist for debugging locally, including the web server, all unit tests, and a single unit test file.

- To build, test, and deploy in a continuous integration environment run `./scripts/run-continuous-integration.sh --image  --version `.

    - This workflow assumes `docker` is logged into whatever registry you attempt to use for storage and that `kubectl` is configured with a context where you can perform a deployment.