simenandre

Setting up a new Next.js project

This document is steps to initiate a Next.js-based setup with our own opinionated Eslint rules and prettier configuration, hosted on Google App Engine.

It's pretty basic, so that the project can grow into something more advanced if needed.

Step 1 – Add default Next.js boilerplate

simenandre

{
  "value": {
    "invoice.charged": {
      "description": "Invoice created and charged",
      "payloadModel": "Invoice",
      "payloadModelClass": "no.tripletex.api2.invoice.InvoiceDTO"
    },
    "supplier.create": {
      "description": "Supplier created",
      "payloadModel": "Supplier",

simenandre

Simen A. W. Olsen

My passion is to create. My drive in life is to build others by creating an everyday life where people feel safe, fulfilled and challenged to be the best version of themself. My background is in software engineering and leadership, and I have run Bjerk for over a decade. We are particularly proud to build software that changes how people think, communicate, and learn, all in the name of making people achieve more.

I contribute to my goals by creating projects, collectives, companies, and relationships with collaboration, sustainability and continuous attention to good design and technical excellence – one step at a time.

simenandre

Label categories

When doing issue refinement, we typically start from these steps:

1. Add kind labels to communicate what kind of issue this is.
2. Add impact labels to communicate how this will impact the project.
3. Potentially add needs labels
4. Add sizing with size labels
5. if bug) add a pX label

simenandre

#!/bin/bash

# Check if environment variables are set
if [ -z "$TURSO_GROUP" ]; then
  echo "Error: TURSO_GROUP environment variable is not set."
  exit 1
fi

if [ -z "$TURSO_BASE_DB" ]; then
  echo "Error: TURSO_BASE_DB environment variable is not set."