Fix staging and goodgo domains issues
Opened this issue · 5 comments
Done
- merged latest
dev
branch intomaster
on both virtualenvs - updated dependencies on the
staging
env - installed geoip database on
staging
env - updated
nginx
confs on all three envs to redirect http traffic to https - updated
uwsgi
confs on all three envs with correct email settings - sending of e-mails should work OK on all of them (I tested only from the staging env) - ran
manage.py migrate
andmanage.py compilemessages
on both virtualenvs - reloaded everything
P.S. - we're starting to need an automated deploy
script for this ;)
yes, but we will need a higher level deployment pipeline including keycloak.
Why did you run migrare twice? Currently goodgo and staging point to the same RDS.
Did you test registration/login/logout (even for multiple users to test any cookie issue)?
Why did you run migrare twice? Currently goodgo and staging point to the same RDS.
I ran migrate on both the smb
and the smb-staging
venvs
Did you test registration/login/logout (even for multiple users to test any cookie issue)?
I did try logging in with the various envs, but not registration
I did try logging in with the various envs, but not registration
We need to test all the workflows, particularly through the goodgo domain.
Sorry, I closed this by mistake (waffle UI misled me)