Files
webstudio/apps/builder/docker-compose.yaml
Ivan Starkov e65ec39eef feat: Support refund events (#2673)
## Description

ref #2661

We use GENERATED columns in our database to simplify field extraction
from events. This avoids using JSON operators in our views. We store the
entire event data. In our SaaS, there's a script that runs once to
populate the eventData. We've also updated the n8n schemas in our SaaS
to automatically fill eventData. This setup makes it quicker to add new
events or update logic in n8n schemas.

## Steps for reproduction


## Code Review

- [ ] hi @kof, I need you to do
  - conceptual review (architecture, feature-correctness)
  - detailed review (read every line)
  - test it on preview

## Before requesting a review

- [ ] made a self-review
- [ ] added inline comments where things may be not obvious (the "why",
not "what")

## Before merging

- [ ] tested locally and on preview environment (preview dev login:
5de6)
- [ ] updated [test
cases](https://github.com/webstudio-is/webstudio/blob/main/apps/builder/docs/test-cases.md)
document
- [ ] added tests
- [ ] if any new env variables are added, added them to `.env.example`
and the `builder/env-check.js` if mandatory
2023-12-07 15:46:49 +02:00

21 lines
423 B
YAML

version: "3.1"
volumes:
db:
services:
db:
image: postgres
# Uncomment to log all queries
command: ["postgres", "-c", "log_statement=all"]
restart: always
environment:
# postgresql://user:pass@localhost:5432/webstudio
POSTGRES_PASSWORD: pass
POSTGRES_DB: webstudio
POSTGRES_USER: user
volumes:
- db:/var/lib/postgresql/data
ports:
- ${PGPORT:-5432}:5432