Closed moorsey closed 1 year ago
manage.py migrate
Many thanks, no dice unfortunately! Maybe not fixable!
docker exec -it tandoor_web_recipes_1 /bin/sh
/opt/recipes # ls
CONTRIBUTERS.md boot.sh makemessages.cmd mediafiles openapitools.json requirements.txt venv yarn.lock
SECURITY.md cookbook manage.py nginx recipes staticfiles vue
/opt/recipes # ./manage.py migrate
Traceback (most recent call last):
File "/opt/recipes/./manage.py", line 8, in <module>
from django.core.management import execute_from_command_line
ModuleNotFoundError: No module named 'django'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/recipes/./manage.py", line 10, in <module>
raise ImportError(
ImportError: Couldn't import Django. Are you sure it's installed and available on your PYTHONPATH environment variable? Did you forget to activate a virtual environment?
OK, tried dropping completely, starting fresh, can get Tandoor up and running OK
Importing the DB works, but obviously there have been a load of changes, but can't force an upgrade of the DB it seems, same django error again
Will look at spinning up an older version of the image I guess for now!
Cheers
OK, so tried 1.4.6 and 1.4.5, restore DB, same error:
The above exception (relation "cookbook_userspace" does not exist LINE 1: SELECT COUNT(*) AS "__count" FROM "cookbook_userspace" WHERE... ^ ) was the direct cause of the following exception:
Very confused as to how there could be anything remaining causing an error now
OK, think I've mixed. I went back to 1.2.7, which worked OK. I then stepped through each version, running...
docker-compose pull docker-compose up -d --remove-orphans
After each version edit, watched web container logs to make sure it completed migrations etc, rinse repeat
All booted up anyway, seems well so far....!
Sorry venv/bin/activate
needs executed first
Have just ran an upgrade:
Get to login page fine, but when logging in get the below traceback
Will try a fresh install later this week and re-import DB, see if that helps, but maybe I am able to manually run DB upgrade? Perhaps something was missed on first run to create new tables etc. Thought I would log in case of a wider issue
Afraid I do not recall the version I came from, ran an upgrade end of last year ish.