Build with Typescript, Prisma and Auth0.com, runs on vercel.com

• Giessdenkiez.de Postgres API

  • Prerequisites
  • Setup
    • Auth0
    • Environment Variables
    • Postgres DB with Prisma
    • Vercel
      • Vercel Environment Variables
  • API Routes
    • API Authorization
  • Develop
  • Tests

• Vercel.com Account
• Auth0.com Account
• Docker PostgresDB + Postgis

Setup your auth0.com account and create a new API. Get your jwksUri, issuer, audience, client_id and client_secret values. The values for client_id and client_secret are only needed if you want to run local tests with tools like rest-client, Postman, Insomnia or Paw. This is explained later in this document.

Rename the file .env.sample to .env and fill in all the values you already have available.

Setup your Postgres + Postgis Database. Maybe on render.com, AWS or whereever you like your relational databases. Take your values for user, database, password, port and host and also add them to the .env file. Make sure that the DATABASE_URL environment variable in the .env file is set right. The pattern is postgresql://USER:PASSWORD@HOST:PORT/DATABASE?schema=SCHEMA. The DATABASE_URL is used by Prisma to connect to your DB. You can have several predefiend URLs in the .env file and just comment them in or out depending with which DB you want to connect.

Run npm run prisma:push:dangerously. The dangerously is here to remind you that this will change your DB without migration. This should only be used for the setup and development. All later changes need to be controlled using prisma migrate or done manually with SQL and synced with prisma pull to If you want some initial data in your DB for testing run also npm run prisma:seed:dangerously. Read the prisma docs for an deeper insight.

Setup your vercel account. You might need to login. Run npx vercel login.

We use Prisma to provision and maintain the database. Run npm run prisma:push:dangerously. The dangerously is here to remind you that this will change your DB without migration. This should only be used for the setup. All later changes need to be controlled using prisma migrate or done manually with SQL and synced with prisma pull to If you want some more data in your DB for testing run also npm npm run prisma:seed:dangerously. Read the prisma docs for an deeper insight.

Add all your environment variables to the Vercel project by running the commands below. The cli will prompt for the values as input and lets you select if they should be added to development, preview and production. For local development you can overwrite these value with an .env file in the root of your project. It is wise to have one remote Postgres DB for production and one for preview. The preview will then be used in deployment previews on GitHub. You can connect your vercel project with your GitHub repository on the vercel backend.

# the user for the postgres db
vercel env add plain user
# the database name
vercel env add plain database
# the database password
vercel env add plain password
# the host of the db, aws? render.com? localhost?
vercel env add plain host
# defaults to 5432
vercel env add plain port
# below are all taken from auth0.com
vercel env add plain jwksuri
vercel env add plain audience
vercel env add plain issuer

To let these variables take effect you need to deploy your application once more.

vercel --prod

Congrats. Your API should be up and running. You might need to request tokens for the your endpoints that need authentification. See the auth0.com docs for more info.

There are 3 main routes /get, /post and /delete.

On the /get route all actions are controlled by passing query strings. On the /post and /delete route you will work with the POST body. You will always have the queryType and sometimes aditional values in all three of them. For example to fetch a specific tree run the following command.

curl --request GET \
  --url 'http://localhost:3000/get?queryType=byid&id=_01_' \

# to see a result from the prodcution api use
# https://giessdenkiez-de-postgres-api.vercel.app/get?queryType=byid&id=_0001wka6l

Some of the request will need an authoriziation header. You can obtain a token by making a request to your auth0 token issuer.

curl --request POST \
  --url https://your-tenant.eu.auth0.com/oauth/token \
  --header 'content-type: application/json' \
  --data '{"client_id": "abc","client_secret": "def","audience": "your-audience","grant_type": "client_credentials"}'
# fill in the dummy fields

This will respond with an access_token. Use it to make autheticated requests.

curl --request POST \
  --url http://localhost:3000/post \
  --header 'authorization: Bearer ACCESS_TOKEN' \
  --header 'content-type: application/json' \
  --data '{"queryType":"adopt","tree_id":"_01","uuid": "auth0|123"}'

Take a look into docs/api.http. The requests in this file can be run with the VSCode extension REST Client.

Start your local postgres DB using docker-compose. docker-compose up. Provision it by running npm run prisma:push:dangerously.

You can run the project locally by running npx vercel dev or npm run vercel:dev in the root of your project. Make sure your values in the .env match the settings for the DB in the docker-compose.yml file.

Locally you will need Docker. Start a DB and run the tests with the following commands.

cd test
# omit the -d if you want to keep it in the foreground
docker-compose -f docker-compose.test.yml up -d
cd ..
npm test

On CI the postgres DB is started automagically. See .github/workflows/tests.yml