c90d2fd5cc
See: https://github.com/twentyhq/twenty/issues/9031#issuecomment-2542015975 I think it would be easier if the default behavior for the container was to run the migration, and setting the environment variable would be used to disable it (e.g. on the worker). Long-term goal is for the default setup to work out of the box with ~2 env variables only (database url, redis url) I don't think there's a big risk if people forget to turn it off on the worker?
62 lines
1.6 KiB
YAML
62 lines
1.6 KiB
YAML
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
labels:
|
|
app: twentycrm-worker
|
|
name: twentycrm-worker
|
|
namespace: twentycrm
|
|
spec:
|
|
progressDeadlineSeconds: 600
|
|
replicas: 1
|
|
strategy:
|
|
rollingUpdate:
|
|
maxSurge: 1
|
|
maxUnavailable: 1
|
|
type: RollingUpdate
|
|
selector:
|
|
matchLabels:
|
|
app: twentycrm-worker
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: twentycrm-worker
|
|
spec:
|
|
containers:
|
|
- name: twentycrm
|
|
image: twentycrm/twenty:latest
|
|
imagePullPolicy: Always
|
|
env:
|
|
- name: SERVER_URL
|
|
value: "https://crm.example.com:443"
|
|
- name: PG_DATABASE_URL
|
|
value: "postgres://postgres:postgres@twentycrm-db.twentycrm.svc.cluster.local/default"
|
|
- name: DISABLE_DB_MIGRATIONS
|
|
value: "false" # it already runs on the server
|
|
- name: STORAGE_TYPE
|
|
value: "local"
|
|
- name: "MESSAGE_QUEUE_TYPE"
|
|
value: "bull-mq"
|
|
- name: "CACHE_STORAGE_TYPE"
|
|
value: "redis"
|
|
- name: "REDIS_URL"
|
|
value: "redis://twentycrm-redis.twentycrm.svc.cluster.local:6379"
|
|
- name: APP_SECRET
|
|
valueFrom:
|
|
secretKeyRef:
|
|
name: tokens
|
|
key: accessToken
|
|
command:
|
|
- yarn
|
|
- worker:prod
|
|
resources:
|
|
requests:
|
|
memory: "1024Mi"
|
|
cpu: "250m"
|
|
limits:
|
|
memory: "2048Mi"
|
|
cpu: "1000m"
|
|
stdin: true
|
|
tty: true
|
|
dnsPolicy: ClusterFirst
|
|
restartPolicy: Always
|