You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the image or git is pulled then started using docker compose up -d the server starts as expected, but using Portainer to launch results in obico-web logs showing:
python: can't open file '/app/manage.py': [Errno 2] No such file or directory
python: can't open file '/app/manage.py': [Errno 2] No such file or directory
python: can't open file '/app/manage.py': [Errno 2] No such file or directory
And obico-tasks logs show:
Usage: celery [OPTIONS] COMMAND [ARGS]...
Try 'celery --help' for help
Error: Invalid value for '-A' / '--app':
Unable to load celery application.
However changing the backend volume in docker-compose.yml from - ./backend:/app to: - ./backend:/backend works
Adding the line -./backend:/appdoes not work.
Is there a reason why the frontend volume points to the frontend directory, but backend points to a directory that doesn't exist in the root folder? Again this is only an issue in Portainer but the fix works for docker compose.
Just want to get a little bit of insight as to why it's set up this way and what I need to fix in a PR to get working on both platforms.
The text was updated successfully, but these errors were encountered:
?: (staticfiles.W004) The directory '/app/../frontend/builds' in the STATICFILES_DIRS setting does not exist.
?: (staticfiles.W004) The directory '/app/../frontend/static' in the STATICFILES_DIRS setting does not exist.
and this error...
ValueError: Missing staticfiles manifest entry for 'vendor/css/sweetalert2.min.css'
When the image or git is pulled then started using
docker compose up -d
the server starts as expected, but using Portainer to launch results in obico-web logs showing:And obico-tasks logs show:
However changing the backend volume in
docker-compose.yml
from- ./backend:/app
to:- ./backend:/backend
worksAdding the line
-./backend:/app
does not work.Is there a reason why the frontend volume points to the frontend directory, but backend points to a directory that doesn't exist in the root folder? Again this is only an issue in Portainer but the fix works for docker compose.
Just want to get a little bit of insight as to why it's set up this way and what I need to fix in a PR to get working on both platforms.
The text was updated successfully, but these errors were encountered: