[recnet-api] Connect environment to rds database and generate DB schema

[joannechen1223]

Description

1. Create a Postgres RDS database in the dev elastic beanstalk environment.
2. Introduce prisma to recnet-api as our db orm.
3. Create db schema by prisma migration based on DB schema doc.
4. Move buildspec.yml to the repository.
5. Create an API GET /user/:handle just for dev testing purposes.
6. Create a shared postman workspace.

Related Issue

• Create an RDS DB instance on AWS and create a DB schema #104
• Connect backend service to RDS #105

Notes

N/A

TODO

• Create development guide for how to do prisma migration

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
rec-net	⬜️ Ignored (Inspect)	Visit Preview		Mar 8, 2024 5:12am

[swh00tw]

I kinda fixed the nx-ignore script lol. See Canceled by Ignored Build Step. Now, it won't rebuild RecNet when there's no change to it.

[swh00tw]

LGTM

[swh00tw]

Should we also add down migration file down.sql for each up migration?

Docs: https://www.prisma.io/docs/orm/prisma-migrate/workflows/generating-down-migrations

[joannechen1223]

Great idea, I will create another PR to add it.

[swh00tw]

[nit]: you can use zod to parse the process.env. For example:

import { z } from "zod"
const PostgreConfigSchema = z.object({
    host: z.string(),
    port: z.number(),
    database: z.string(),
    username: z.string(),
    password: z.string(),
})

const postgresConfig = PostgreConfigSchema.parse(process.env)

The error message would be better since zod would tell you which field exactly is invalid or unexpected, instead of error like this PrismaClientInitializationError: The provided database string is invalid. Error parsing connection string: invalid port number in database URL. Please refer to the documentation in https://www.prisma.io/docs/reference/database-reference/connection-urls for constructing a correct connection string. In some cases, certain characters must be escaped. Please check the string for any illegal characters. It makes it easier to debug if any env var is missing.

[swh00tw]

Same thing apply to process.env.DB_MIGRATE & process.env.PRISMA_SCHEMA. Personally, I always use zod to parse the whole env variables, use EnvSchema or something to prevent me directly accessing the process.env, it's error-prone and easy to have typos.

[joannechen1223]

I tend to use the config service provided by nestJS to deal with these configs. I will create another PR to enhance the configuration management and will consider to take in this advice.