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

One of the considerations for any module written in Deno is whether it is best
to have one central dependency file, or if each file should only import the
respectively needed modules. There are pros and cons with both ways, and I use
either depending on the situation. Most libraries you come across will most
likely have one 

 to keep versioning simple across the codebase.


but these are more often used by applications, and you will most likely never
see them being used in modules.

For the sake of this lesson, we will create a separate 

 file so that
you can get comfortable with importing local files.

Create a new folder (you can name it after the title of this page) and add two
files: 

. In the last step, we added the imports to our

, but this time we will add the external imports into our 

export { green, red } from "https://deno.land/std@0.155.0/fmt/colors.ts";
export { serve } from "https://deno.land/std@0.155.0/http/server.ts";

 to export the values to
our other files.

Now it is time to create the server. Now that we have all our dependencies in

, we can import them from there. We start by adding 

 file should now only have one line
of code.

---
title: How to Start a Deno Server and Set Permissions
description: We will build our first server in Deno
---

## Deno server

One of the considerations for any module written in Deno is whether it is best
to have one central dependency file, or if each file should only import the
respectively needed modules. There are pros and cons with both ways, and I use
either depending on the situation. Most libraries you come across will most
likely have one `deps.ts` to keep versioning simple across the codebase.

> Deno also supports
> [import maps](https://deno.land/manual/linking_to_external_code/import_maps)
> but these are more often used by applications, and you will most likely never
> see them being used in modules.

For the sake of this lesson, we will create a separate `deps.ts` file so that
you can get comfortable with importing local files.

Create a new folder (you can name it after the title of this page) and add two
files: `deps.ts` and `main.ts`. In the last step, we added the imports to our
`main.ts`, but this time we will add the external imports into our `deps.ts`
file.

Add the following imports to `deps.ts`:

```typescript { actualFilename=../../code/module_1.4/deps.ts endChar=144 endLine=3 startChar=0 startLine=1 statedFilename=deps.ts url=https&#x3A;//gitlab.com/fullstackio/books/build-and-deploy-a-rest-api-with-deno/module_01/lesson_04/.../code/module_1.4/deps.ts }
export { green, red } from "https://deno.land/std@0.155.0/fmt/colors.ts";
export { serve } from "https://deno.land/std@0.155.0/http/server.ts";
```

> Notice that we are using `export` instead of `import` to export the values to
> our other files.

Now it is time to create the server. Now that we have all our dependencies in
`deps.ts`, we can import them from there. We start by adding `green` and `serve`
to our imports in `main.ts`. Your `main.ts` file should now only have one line
of code.

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