Welcome to Build and Deploy a REST API with Deno!

How to Install Deno Locally and in Docker Containers

Introduction

Deno vs Node: A Deno Fresh Start to JavaScript Runtimes

How to Use the Deno REPL Command Line Interface

Executing TypeScript Files With Deno With the Config File

Deno vs Golang's Standard Library

How to Start a Deno Server and Set Permissions

How to Build a Token Authentication Server With Deno

Getting Started with Deno

Using Databases with Deno

How to Use PostgreSQL in Docker with Deno

How to Integrate MySQL or MariaDB With Deno

How to Add SQLite to Deno with deno-sqlite

Connect to a database

What is Database Migration? The Strategy to Migrate Data

How to Add Nessie to Deno to Migrate Databases

How to Create a New Database Migration With Deno Nessie

Edit a Deno Nessie Database Migration to Catch Errors

How to Run and Roll Back a Database Migration With Deno Nessie

How to Create a Database Seed File With Deno Nessie

How to Import JSON Data and Seed a Database With Deno Nessie

Database migrations

REST API Introduction

Best Practices for a REST API: Endpoints and Database Schema

How to Prepare Deno to Build a REST API

How to Build REST API Endpoints in Deno

Integrate a PostgreSQL Database With Nessie Into a Deno API

Building a MySQL or PostgreSQL Database Pool in Deno

Migrating Data to PostgreSQL and Modeling Data in Deno

Build API Calls That Generate SQL Queries in Deno

Create a Database Controller in Deno

How to Authenticate and Authorize REST API Requests in Deno

Create New Tables and Models With Deno Database Migration

Add List, Create, Read, Update, and Delete Requests in Deno

How to Build Many-to-Many Namespace Connections in Deno

API Afterthoughts

REST API

Deployment Introduction

How to Create a Docker Image to Containerize an Application

How to Create Continuous Integration Files for GitHub and GitLab

How to Deploy a Deno API Server With the Digital Ocean API

How to Deploy a Deno Docker Image to Digital Ocean

Deploy with Docker

Deployment

deno

In this course, we will learn how to work with [Deno](https://deno.land) to create a REST API using TypeScript with the web framework [Oak](https://github.com/oakserver/oak) and the migration tool [Nessie](https://github.com/halvardssm/deno-nessie). 
Deno is a JavaScript runtime created by [Ryan Dahl](https://tinyclouds.org), the same creator for Node, as an attempt to simplify the JavaScript landscape by strictly following the WebAPI specs. 
If you are interested in learning more about the motivation behind Deno, you can watch this video where Ryan Dahl explains "[10 Things I Regret About Node.js](https://www.youtube.com/watch?v=M3BM9TB-8yA)"

We will explore how to create an application using the powers of TypeScript, and learn how to traverse the Deno ecosystem which is much like the native web ecosystem. 
There are 5 modules that will take you from installing Deno and running your first lines of code, to working with web frameworks and databases, and in the end, deploying your application to a web server using a deployment pipeline.

Throughout this course, you will experience all the different aspects of Deno which you will need to create your own application in the future. 
And from this course, you will get a good feeling for if Deno is ready to be your next default for new projects.

In this course, we will learn how to create and deploy a REST API with Deno from scratch.

Build and deploy a REST API with Deno

Integrating databases into your application

Importance of database migrations in production applications

Deploying Deno applications to production using CICD

No matter which of the deployment plans you choose, you will need a build
pipeline. There are many third-party tools out there such as

, but to keep it simple, I will be using the
vanilla GitLab and GitHub pipelines.

As most of you probably have a GitHub account, I will be starting with this one.

The GitHub CI is activated for your repository when you have a

 folder with a YAML workflow file. This file can be called
pretty much whatever you want, and you can have as many workflow files as you
want. See more information about the configuration


if you are interested. When you make any file changes to your repository on
GitHub (push, merge, pr etc.), GitHub will check your 

 folder
and each of the jobs to see if any of them can be executed. There is currently
no way to trigger the jobs manually, but you can rerun past jobs if needed.

name: CI

env:
  DENO_VERSION: 1.26.0

on:
  push:
    branches:
      - main

jobs:
  lint-and-format-check:
    runs-on: ubuntu-latest
    steps:
      - name: Clone repo
        uses: actions/checkout@v3

      - name: Install deno
        uses: denoland/setup-deno@v1
        with:
          deno-version: ${{env.DENO_VERSION}}

      - name: Deno formatting
        run: deno fmt --check

      - name: Deno linting
        run: deno lint

, then set an environment variable for our Deno
version. We also want to only run the deployment for the 

 branch, but we
want to allow it for all pushes. This is of course dependent on your
requirements, but for this tutorial, it will serve as a good start.

---
title: Continuous Integration
description: You will learn how to create a basic CI file for GitHub and GitLab, and run tests on them
---

## Continuous Integration (CI)

No matter which of the deployment plans you choose, you will need a build
pipeline. There are many third-party tools out there such as
[Jenkins](https://www.jenkins.io/), [Travis CI](https://travis-ci.org/), and
[Circle CI](https://circleci.com/), but to keep it simple, I will be using the
vanilla GitLab and GitHub pipelines.

### GitHub

As most of you probably have a GitHub account, I will be starting with this one.

The GitHub CI is activated for your repository when you have a
`/.github/workflows` folder with a YAML workflow file. This file can be called
pretty much whatever you want, and you can have as many workflow files as you
want. See more information about the configuration
[here](https://docs.github.com/en/actions/learn-github-actions/introduction-to-github-actions)
if you are interested. When you make any file changes to your repository on
GitHub (push, merge, pr etc.), GitHub will check your `.github/workflows` folder
and each of the jobs to see if any of them can be executed. There is currently
no way to trigger the jobs manually, but you can rerun past jobs if needed.

Let's start by creating our YAML file: `/.github/workflows/ci.yml`, and adding
the following to it:

```typescript { actualFilename=../../code/module_5.2/.github/workflows/ci.yml endChar=444 endLine=28 startChar=0 startLine=1 statedFilename=ci.yml url=https&#x3A;//gitlab.com/fullstackio/books/build-and-deploy-a-rest-api-with-deno/module_05/lesson_02/.../code/module_5.2/.github/workflows/ci.yml }
name: CI

env:
  DENO_VERSION: 1.26.0

on:
  push:
    branches:
      - main

You will learn how to create a basic CI file for GitHub and GitLab, and run tests on them

Learn

The newline Guide to Building Your First GraphQL Server with Node and TypeScript

Teach

Amelia Wattenberger

Author of Fullstack D3

Community

Build and deploy a REST API with Deno

Module 1: Introduction

Introduction:

Start Here

Introduction:

Welcome to Build and Deploy a REST API with Deno!

Lesson:

How to Install Deno Locally and in Docker Containers

Module 2: Getting Started with Deno

Introduction:

Deno vs Node: A Deno Fresh Start to JavaScript Runtimes

Lesson 1:

How to Use the Deno REPL Command Line Interface

Lesson 2:

Executing TypeScript Files With Deno With the Config File

Lesson 3:

Deno vs Golang's Standard Library

Lesson 4:

How to Start a Deno Server and Set Permissions

Lesson 5:

How to Build a Token Authentication Server With Deno

Module 3: Connect to a database

Introduction:

Using Databases with Deno

Lesson 1:

How to Use PostgreSQL in Docker with Deno

Lesson 2:

How to Integrate MySQL or MariaDB With Deno

Lesson 3:

How to Add SQLite to Deno with deno-sqlite

Module 4: Database migrations

Introduction:

What is Database Migration? The Strategy to Migrate Data

Lesson 1:

How to Add Nessie to Deno to Migrate Databases

Lesson 2:

How to Create a New Database Migration With Deno Nessie

Lesson 3:

Edit a Deno Nessie Database Migration to Catch Errors

Lesson 4:

How to Run and Roll Back a Database Migration With Deno Nessie

Lesson 5:

How to Create a Database Seed File With Deno Nessie

Lesson 6:

How to Import JSON Data and Seed a Database With Deno Nessie

Module 5: REST API

Introduction:

REST API Introduction

Lesson 1:

Best Practices for a REST API: Endpoints and Database Schema

Lesson 2:

How to Prepare Deno to Build a REST API

Lesson 3:

How to Build REST API Endpoints in Deno

Lesson 4:

Integrate a PostgreSQL Database With Nessie Into a Deno API

Lesson 5:

Building a MySQL or PostgreSQL Database Pool in Deno

Lesson 6:

Migrating Data to PostgreSQL and Modeling Data in Deno

Lesson 7:

Build API Calls That Generate SQL Queries in Deno

Lesson 8:

Create a Database Controller in Deno

Lesson 9:

How to Authenticate and Authorize REST API Requests in Deno

Lesson 10:

Create New Tables and Models With Deno Database Migration

Lesson 11:

Add List, Create, Read, Update, and Delete Requests in Deno

Lesson 12:

How to Build Many-to-Many Namespace Connections in Deno

Lesson 1:

API Afterthoughts