Starting template for nest-prisma development under the city of Bratislava.
If you want to run an application without installing it locally quickly, you can run it through docker-compose:
docker-compose up --build- Run npm installation for dependencies
npm install- For Prisma, it comes in handy to have Prisma cli. Check if it is working on your pc:
npx prisma- Check the
.envfile for your correct local database connection configuration. It looks like this:
DATABASE_URL="postgresql://user:password@localhost:5432/mydatabase?schema=public"`If you have issues connecting to your Postgres, maybe you need to set timeout connect_timeout. Sometimes macs have problems with that:
DATABASE_URL="postgresql://user:password@localhost:5432/?connect_timeout=30&schema=public"# development
npm run start
# watch mode
npm run start:dev
# production mode
npm run start:prodTo run tests in the repo, please use these commands:
# unit tests
npm run test
# e2e tests
npm run test:e2e
# test coverage
npm run test:covWe have multiple options for deploying your app to our Kubernetes cluster.
TODO
You can use our bratiska-cli, which takes care of deploying the app.
-
First, install the utility:
yarn global add bratislava/bratiska-cli
-
then go to folder of
/strapior/nextand run just this command:bartiska-cli deploy
That`s all, everything should run automatically and if not you will be notified. You can also check user guide of bratiska-cli.
- To initialize Prisma for the first time, you can run: (but it deletes old Prisma schema if it is available there)
prisma initIf you have some change in the schema.prisma, run:
npx prisma db pushThis will update the structure. But if you have some existing data in db, you need to create migrations to propagate changes properly.
npx prisma migrate dev --name initThis Prisma migrates dev command generates SQL files and directly runs them against the database. In this case, the following migration files were created in the existing Prisma directory:
We are using Prisma schema with the name schema.deployment.prisma, which has specified build target to our Kubernetes server for deployment.
To build the image for the development run:
docker build --target dev .and for a production run:
docker build --target prod .You can manually create a local image and push it to the repository if you are interested.
You can decide which image you would like to build (dev or production) based on your preference.
docker build -t harbor.bratislava.sk/standalone/nest-prisma-template:manual --target prod . Push image to harbor
docker push harbor.bratislava.sk/standalone/nest-prisma-template:manualIf you don`t have Kustomize, please install it:
brew install kustomizeGenerating kustomize file from source files:
kustomize build --load-restrictor LoadRestrictionsNone kubernetes/envs/Dev | envsubst > manifest.ymlLet's have a look if you are in the proper cluster:
kubectl config current-contextWe are using for secrets Sealed Secrets https://github.com/bitnami-labs/sealed-secrets.
To use a secret in your project, you have to install kubeseal if you haven`t installed it yet.
brew install kubesealThe next thing is going to the folder secrets where all our secrets are stored:
cd kubernetes/base/secretsAfter that, we need to create a temp file for our new secrets. Let's assume we want database connection secretes. You need to make this file database.yml
apiVersion: v1
kind: Secret
metadata:
name: database-secret
annotation:
sealedsecrets.bitnami.com/managed: "true"
data:
POSTGRES_DB: YmFuYW5h
POSTGRES_USER: YmFuYW5h
POSTGRES_PASSWORD: YmFuYW5hmetadata.nameis the name of the group of secrets in our case,database-secretannotation/sealedsecrets.bitnamiadd this to automatically create unsealed secret in kubernetes clusterdatacontains environment variables keys (POSTGRES_DB) and base64 encode values (YmFuYW5h)
For example, if you need to set up the database name to banana, you need to base64 encode this value. You can use an online base64 converter like https://www.base64encode.org and encode banana to YmFuYW5h.
The last thing is encrypting our secrets by kubeseal to be used on Kubernetes. You need to run this command that creates the file database.secret.yml where all our values are encrypted and safe to add to the repository.
kubeseal --controller-name=sealed-secrets --scope=namespace-wide --namespace=standalone --format=yaml < database.yml > database.secret.yml If you want to propagate a sealed secret to Kubernetes without a pipeline, you can run this command:
kubectl create -f database.secret.ymlIf you already have a sealed secret in Kubernetes, you can update it with the command:
kubectl apply -f database.secret.ymlUsually, you get this kind of error: Error from server (AlreadyExists): error when creating "database.secret.yml": sealedsecrets.bitnami.com "nest-Prisma-template-database-secret" already exists
If you want to check if your secret is there, you can run this command:
kubectl get secret --namespace=standalone nest-prisma-template-database-secretPlease use our services as database name and user the project slug. In this case, we will use nest-prisma-template. And for passwords, use at least 16 characters long pass with random chars.
POSTGRES_DB: nest-prisma-template
POSTGRES_USER: nest-prisma-template
POSTGRES_PASSWORD: LBcdso08b&aasd(ck2*d!pwhich after base64 encoding looks like this:
POSTGRES_DB: bmVzdC1wcmlzbWEtdGVtcGxhdGU=
POSTGRES_USER: bmVzdC1wcmlzbWEtdGVtcGxhdGU=
POSTGRES_PASSWORD: TEJjZHNvMDhiJmFhc2QoY2syKmQhcA==Sometime when you have project not yet in production, and DB schema is developing, you can reset DB to apply new changes instead of pilling migrations.
Open terminal with postgress pod and log in:
psql -U nest-forms-backendthen run these commands:
DROP SCHEMA public CASCADE;
CREATE SCHEMA public;
GRANT ALL ON SCHEMA public TO "nest-forms-backend";
GRANT ALL ON SCHEMA public TO public;- Website - https://inovacie.bratislava.sk/