greg [iero]
greg [iero]
TTwenty
Created by Krzysztof Cieśllik on 8/30/2024 in #❓︱help
Is it possible to host it using synology?
Did you tried to put the synology IP in SERVER_URL (.env file) ?
12 replies
TTwenty
Created by greg [iero] on 8/27/2024 in #❓︱help
White empty page (Token expired)
They are working on a fix
16 replies
TTwenty
Created by greg [iero] on 8/27/2024 in #❓︱help
White empty page (Token expired)
For @Raph : in your .env:
ACCESS_TOKEN_EXPIRES_IN=7d
ACCESS_TOKEN_EXPIRES_IN=7d
(note the 'S' at expireS) and in docker-compose file:
server:
environment:
ACCESS_TOKEN_EXPIRES_IN: ${ACCESS_TOKEN_EXPIRES_IN}
server:
environment:
ACCESS_TOKEN_EXPIRES_IN: ${ACCESS_TOKEN_EXPIRES_IN}
and it works now
16 replies
TTwenty
Created by greg [iero] on 8/27/2024 in #❓︱help
White empty page (Token expired)
-> PM
16 replies
TTwenty
Created by greg [iero] on 8/27/2024 in #❓︱help
White empty page (Token expired)
Hi @charles No change with ACCESS_TOKEN_EXPIRE_IN=7d, I have the empty page this morning again I'm available for a call if you need to test something for the fix!
16 replies
TTwenty
Created by greg [iero] on 8/27/2024 in #❓︱help
White empty page (Token expired)
thanks, @charles
16 replies
TTwenty
Created by greg [iero] on 8/27/2024 in #❓︱help
White empty page (Token expired)
I enforced those parameters:
ACCESS_TOKEN_EXPIRE_IN=30m
REFRESH_TOKEN_EXPIRES_IN=7d
ACCESS_TOKEN_EXPIRE_IN=30m
REFRESH_TOKEN_EXPIRES_IN=7d
But no change.
16 replies
TTwenty
Created by greg [iero] on 8/27/2024 in #❓︱help
White empty page (Token expired)
Tested on Safari and Firefox, same behaviour
16 replies
TTwenty
Created by Nathan on 7/26/2024 in #❓︱help
Data Migration to another host.
For the record, my backup script :
#!/bin/bash

export DEST="/home/iero/twenty/backup"
export PGPASSWORD="blablabla"

now=`date +"%Y-%m-%d"`

pg_dump postgres://twenty:${PGPASSWORD}@localhost:5432/default | gzip > ${DEST}/db_${now}.sql.gz
#!/bin/bash

export DEST="/home/iero/twenty/backup"
export PGPASSWORD="blablabla"

now=`date +"%Y-%m-%d"`

pg_dump postgres://twenty:${PGPASSWORD}@localhost:5432/default | gzip > ${DEST}/db_${now}.sql.gz
(And yes after I have other scripts that move the files on other locations)
58 replies
TTwenty
Created by Nathan on 7/26/2024 in #❓︱help
Data Migration to another host.
Hi @Nathan What I do (and I use the same logic to backup my prod server): On old server :
pg_dump postgres://twenty:twenty@localhost:5432/default > db_today.sql
pg_dump postgres://twenty:twenty@localhost:5432/default > db_today.sql
On new server :
dropdb -U twenty -h localhost -p 5432 default
createdb -U twenty -h localhost -p 5432 default

psql postgres://twenty:twenty@localhost:5432/default < db_today.sql
dropdb -U twenty -h localhost -p 5432 default
createdb -U twenty -h localhost -p 5432 default

psql postgres://twenty:twenty@localhost:5432/default < db_today.sql
58 replies
TTwenty
Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Thanks a lot @marie @charles , I pushed the same correction to my production server and everything is working well
36 replies
TTwenty
Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
I get those errors
36 replies
TTwenty
Created by marie on 7/16/2024 in #🏡︱general
v0.22 upgrade warnings
Hello @marie and @charles, same for me after updating from 0.21 to 0.22. When I enter:
yarn command:prod workspace:sync-metadata -f
yarn command:prod workspace:sync-metadata -f
36 replies
TTwenty
Created by greg [iero] on 7/12/2024 in #❓︱help
Create entries in GraphQL
Hello @charles Thanks for the tip with network, I will play with that and I will post the answer for others when I will get it 🙂
12 replies
TTwenty
Created by greg [iero] on 7/9/2024 in #❓︱help
Upgrading 0.2 to 0.21
I have this error, don't know if related:
2024-07-11 14:28:46 [Nest] 1 - 07/11/2024, 12:28:46 PM ERROR [SyncDriver] No handler found for job: webhook-queue
2024-07-11 14:29:38 [Nest] 1 - 07/11/2024, 12:29:38 PM ERROR [SyncDriver] No handler found for job: webhook-queue
2024-07-11 14:29:38 [Nest] 1 - 07/11/2024, 12:29:38 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
2024-07-11 14:29:38 [Nest] 1 - 07/11/2024, 12:29:38 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
2024-07-11 14:29:45 [Nest] 1 - 07/11/2024, 12:29:45 PM ERROR [SyncDriver] No handler found for job: webhook-queue
2024-07-11 14:29:45 [Nest] 1 - 07/11/2024, 12:29:45 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
2024-07-11 14:29:45 [Nest] 1 - 07/11/2024, 12:29:45 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
2024-07-11 14:28:46 [Nest] 1 - 07/11/2024, 12:28:46 PM ERROR [SyncDriver] No handler found for job: webhook-queue
2024-07-11 14:29:38 [Nest] 1 - 07/11/2024, 12:29:38 PM ERROR [SyncDriver] No handler found for job: webhook-queue
2024-07-11 14:29:38 [Nest] 1 - 07/11/2024, 12:29:38 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
2024-07-11 14:29:38 [Nest] 1 - 07/11/2024, 12:29:38 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
2024-07-11 14:29:45 [Nest] 1 - 07/11/2024, 12:29:45 PM ERROR [SyncDriver] No handler found for job: webhook-queue
2024-07-11 14:29:45 [Nest] 1 - 07/11/2024, 12:29:45 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
2024-07-11 14:29:45 [Nest] 1 - 07/11/2024, 12:29:45 PM ERROR [SyncDriver] No handler found for job: entity-events-to-db-queue
28 replies
TTwenty
Created by greg [iero] on 7/9/2024 in #❓︱help
Upgrading 0.2 to 0.21
@charles I don't see any specific error when I navigate after the upgrade. Only those above when I start the container
28 replies
TTwenty
Created by greg [iero] on 7/9/2024 in #❓︱help
Upgrading 0.2 to 0.21
I don't use S3, firebase and others, so I don't think it's bad but I don't know
28 replies
TTwenty
Created by greg [iero] on 7/9/2024 in #❓︱help
Upgrading 0.2 to 0.21
@charles Ok I get it, I will launch the commands in test env and after in prod 🙂 I have those errors when I restart the server:
28 replies
TTwenty
Created by greg [iero] on 7/9/2024 in #❓︱help
Upgrading 0.2 to 0.21
If I restart the container just after, I get the same errors
28 replies