[root@local-rocky admin-jobs]# docker run -it -p 8080:5150 -e LOCO_ENV=production -e WORKER_KIND=Postgres -e CONNECTION_STRING="postgres://postgres:123456@host.docker.internal:5432/anyplay" loco-job-admin
2025-04-17T03:55:42.344415Z INFO loco_rs::config: loading environment from selected_path="config/production.yaml"
2025-04-17T03:55:42.345405Z WARN loco_rs::boot: pretty backtraces are enabled (this is great for development but has a runtime cost for production. disable with logger.pretty_backtrace in your config yaml)
2025-04-17T03:55:42.345622Z INFO loco_rs::boot: initializers loaded initializers="view-engine"
2025-04-17T03:55:42.353646Z INFO loco_rs::controller::app_routes: [GET] /_ping
2025-04-17T03:55:42.353759Z INFO loco_rs::controller::app_routes: [GET] /
2025-04-17T03:55:42.353805Z INFO loco_rs::controller::app_routes: [GET] /jobs/search
2025-04-17T03:55:42.353850Z INFO loco_rs::controller::app_routes: [DELETE] /jobs/:id
2025-04-17T03:55:42.354145Z INFO loco_rs::controller::app_routes: [POST] /jobs/retry/:id
2025-04-17T03:55:42.354235Z INFO loco_rs::controller::app_routes: +middleware name="limit_payload"
2025-04-17T03:55:42.354302Z INFO loco_rs::controller::app_routes: +middleware name="catch_panic"
2025-04-17T03:55:42.354379Z INFO loco_rs::controller::app_routes: +middleware name="etag"
2025-04-17T03:55:42.354671Z INFO loco_rs::controller::app_routes: +middleware name="static"
2025-04-17T03:55:42.354746Z INFO loco_rs::controller::app_routes: +middleware name="logger"
2025-04-17T03:55:42.354794Z INFO loco_rs::controller::app_routes: +middleware name="request_id"
2025-04-17T03:55:42.354843Z INFO loco_rs::controller::app_routes: +middleware name="fallback"
2025-04-17T03:55:42.355097Z INFO loco_rs::controller::app_routes: +middleware name="powered_by"
2025-04-17T03:55:42.355186Z ERROR admin_panel::shared::config: connection settings not found in configuration file environment=production
Error: Message("Connection to worker not configure")
[root@local-rocky admin-jobs]# docker run -it -p 8080:5150 -e LOCO_ENV=production -e WORKER_KIND=Postgres -e CONNECTION_STRING="postgres://postgres:123456@192.168.88.150:5432/anyplay" loco-job-admin
2025-04-17T03:57:33.652046Z INFO loco_rs::config: loading environment from selected_path="config/production.yaml"
2025-04-17T03:57:33.653118Z WARN loco_rs::boot: pretty backtraces are enabled (this is great for development but has a runtime cost for production. disable with logger.pretty_backtrace in your config yaml)
2025-04-17T03:57:33.653338Z INFO loco_rs::boot: initializers loaded initializers="view-engine"
2025-04-17T03:57:33.662724Z INFO loco_rs::controller::app_routes: [GET] /_ping
2025-04-17T03:57:33.662837Z INFO loco_rs::controller::app_routes: [GET] /
2025-04-17T03:57:33.663134Z INFO loco_rs::controller::app_routes: [GET] /jobs/search
2025-04-17T03:57:33.663206Z INFO loco_rs::controller::app_routes: [DELETE] /jobs/:id
2025-04-17T03:57:33.663262Z INFO loco_rs::controller::app_routes: [POST] /jobs/retry/:id
2025-04-17T03:57:33.663381Z INFO loco_rs::controller::app_routes: +middleware name="limit_payload"
2025-04-17T03:57:33.663468Z INFO loco_rs::controller::app_routes: +middleware name="catch_panic"
2025-04-17T03:57:33.663522Z INFO loco_rs::controller::app_routes: +middleware name="etag"
2025-04-17T03:57:33.663722Z INFO loco_rs::controller::app_routes: +middleware name="static"
2025-04-17T03:57:33.663844Z INFO loco_rs::controller::app_routes: +middleware name="logger"
2025-04-17T03:57:33.664053Z INFO loco_rs::controller::app_routes: +middleware name="request_id"
2025-04-17T03:57:33.664138Z INFO loco_rs::controller::app_routes: +middleware name="fallback"
2025-04-17T03:57:33.664231Z INFO loco_rs::controller::app_routes: +middleware name="powered_by"
2025-04-17T03:57:33.664359Z ERROR admin_panel::shared::config: connection settings not found in configuration file environment=production
I want to test the loco worker function, but after deployment, only sqlite dev mode can run normally. I want to use psql mode and product mode, but it can't run and keeps prompting that the configuration cannot be found. I tried to unpack the image to view the configuration file. It exists, but I guess it can't read the variables specified in our env. I tried for a day without success. I gave up... I can only view it through loco jobs dump because it does not provide a list command.
[root@local-rocky admin-jobs]# docker run -it -p 8080:5150 -e LOCO_ENV=production -e WORKER_KIND=Postgres -e CONNECTION_STRING="postgres://postgres:123456@host.docker.internal:5432/anyplay" loco-job-admin
2025-04-17T03:55:42.344415Z INFO loco_rs::config: loading environment from selected_path="config/production.yaml"
2025-04-17T03:55:42.345405Z WARN loco_rs::boot: pretty backtraces are enabled (this is great for development but has a runtime cost for production. disable with
logger.pretty_backtracein your config yaml)2025-04-17T03:55:42.345622Z INFO loco_rs::boot: initializers loaded initializers="view-engine"
2025-04-17T03:55:42.353646Z INFO loco_rs::controller::app_routes: [GET] /_ping
2025-04-17T03:55:42.353759Z INFO loco_rs::controller::app_routes: [GET] /
2025-04-17T03:55:42.353805Z INFO loco_rs::controller::app_routes: [GET] /jobs/search
2025-04-17T03:55:42.353850Z INFO loco_rs::controller::app_routes: [DELETE] /jobs/:id
2025-04-17T03:55:42.354145Z INFO loco_rs::controller::app_routes: [POST] /jobs/retry/:id
2025-04-17T03:55:42.354235Z INFO loco_rs::controller::app_routes: +middleware name="limit_payload"
2025-04-17T03:55:42.354302Z INFO loco_rs::controller::app_routes: +middleware name="catch_panic"
2025-04-17T03:55:42.354379Z INFO loco_rs::controller::app_routes: +middleware name="etag"
2025-04-17T03:55:42.354671Z INFO loco_rs::controller::app_routes: +middleware name="static"
2025-04-17T03:55:42.354746Z INFO loco_rs::controller::app_routes: +middleware name="logger"
2025-04-17T03:55:42.354794Z INFO loco_rs::controller::app_routes: +middleware name="request_id"
2025-04-17T03:55:42.354843Z INFO loco_rs::controller::app_routes: +middleware name="fallback"
2025-04-17T03:55:42.355097Z INFO loco_rs::controller::app_routes: +middleware name="powered_by"
2025-04-17T03:55:42.355186Z ERROR admin_panel::shared::config: connection settings not found in configuration file environment=production
Error: Message("Connection to worker not configure")
[root@local-rocky admin-jobs]# docker run -it -p 8080:5150 -e LOCO_ENV=production -e WORKER_KIND=Postgres -e CONNECTION_STRING="postgres://postgres:123456@192.168.88.150:5432/anyplay" loco-job-admin
2025-04-17T03:57:33.652046Z INFO loco_rs::config: loading environment from selected_path="config/production.yaml"
2025-04-17T03:57:33.653118Z WARN loco_rs::boot: pretty backtraces are enabled (this is great for development but has a runtime cost for production. disable with
logger.pretty_backtracein your config yaml)2025-04-17T03:57:33.653338Z INFO loco_rs::boot: initializers loaded initializers="view-engine"
2025-04-17T03:57:33.662724Z INFO loco_rs::controller::app_routes: [GET] /_ping
2025-04-17T03:57:33.662837Z INFO loco_rs::controller::app_routes: [GET] /
2025-04-17T03:57:33.663134Z INFO loco_rs::controller::app_routes: [GET] /jobs/search
2025-04-17T03:57:33.663206Z INFO loco_rs::controller::app_routes: [DELETE] /jobs/:id
2025-04-17T03:57:33.663262Z INFO loco_rs::controller::app_routes: [POST] /jobs/retry/:id
2025-04-17T03:57:33.663381Z INFO loco_rs::controller::app_routes: +middleware name="limit_payload"
2025-04-17T03:57:33.663468Z INFO loco_rs::controller::app_routes: +middleware name="catch_panic"
2025-04-17T03:57:33.663522Z INFO loco_rs::controller::app_routes: +middleware name="etag"
2025-04-17T03:57:33.663722Z INFO loco_rs::controller::app_routes: +middleware name="static"
2025-04-17T03:57:33.663844Z INFO loco_rs::controller::app_routes: +middleware name="logger"
2025-04-17T03:57:33.664053Z INFO loco_rs::controller::app_routes: +middleware name="request_id"
2025-04-17T03:57:33.664138Z INFO loco_rs::controller::app_routes: +middleware name="fallback"
2025-04-17T03:57:33.664231Z INFO loco_rs::controller::app_routes: +middleware name="powered_by"
2025-04-17T03:57:33.664359Z ERROR admin_panel::shared::config: connection settings not found in configuration file environment=production
I want to test the loco worker function, but after deployment, only sqlite dev mode can run normally. I want to use psql mode and product mode, but it can't run and keeps prompting that the configuration cannot be found. I tried to unpack the image to view the configuration file. It exists, but I guess it can't read the variables specified in our env. I tried for a day without success. I gave up... I can only view it through loco jobs dump because it does not provide a list command.