Hello.
I am now trying to Deploy Self-hosted Retool on AWS Fargate and ECS with CloudFormation.
ECS deployment with fargate.yaml using this document as a reference. I executed it.
The following error occurs and the service fails to start.
|2024-02-06T17:31:20.407+09:00not untarring the bundle|not untarring the bundle|
||2024-02-06T17:31:20.827+09:00sed: can't read ./dist/mobile/*.js: No such file or directory|sed: can't read ./dist/mobile/*.js: No such file or directory|
||2024-02-06T17:31:21.383+09:00{ "level": "info", "message": "[process service types] JOBS_RUNNER", "timestamp": "2024-02-06T08:31:21.382Z" }|{"level":"info","message":"[process service types] JOBS_RUNNER","timestamp":"2024-02-06T08:31:21.382Z"}|
||2024-02-06T17:31:21.446+09:00Warning: POSTGRES_SSL_REJECT_UNAUTHORIZED is currently set to 'false'. This will default to 'true' in a future version of Retool, which may break connections to databases with self-signed SSL/TLS certificates. To prepare for this change, either explicitly set POSTGRES_SSL_REJECT_UNAUTHORIZED=false or configure a custom certificate chain by setting POSTGRES_CUSTOM_SSL_CERT_PATH & POSTGRES_CUSTOM_SSL_CA_FILE_NAME (and optionally POSTGRES_CUSTOM_SSL_CERT_FILE_NAME & POSTGRES_CUSTOM_SSL_KEY_FILE_NAME) — see https://docs.retool.com/docs/environment-variables.|Warning: POSTGRES_SSL_REJECT_UNAUTHORIZED is currently set to 'false'. This will default to 'true' in a future version of Retool, which may break connections to databases with self-signed SSL/TLS certificates. To prepare for this change, either explicitly set POSTGRES_SSL_REJECT_UNAUTHORIZED=false or configure a custom certificate chain by setting POSTGRES_CUSTOM_SSL_CERT_PATH & POSTGRES_CUSTOM_SSL_CA_FILE_NAME (and optionally POSTGRES_CUSTOM_SSL_CERT_FILE_NAME & POSTGRES_CUSTOM_SSL_KEY_FILE_NAME) — see https://docs.retool.com/docs/environment-variables.|
||2024-02-06T17:31:21.780+09:00|Database migrations are up to date.|
I have basically followed the procedure, but do I need to do anything else special?