Back
Similar todos
Load previous page…
more 
#djangopackages work including a Django 3.2 upgrade
🔼 Upgraded to Django 2.2 LTS 
#conf
2. solve the data migration for 2 houses ✅ #enpvqp
- the sqlite issue ✅ #enpvqp
4. deploy new version ✅ #enpvqp
4. deploy new version ✅ #enpvqp
deploy new version for #enpvqp
- automate the csv updating ✅ #enpvqp
⬆️ upgraded #djangopackages to Django 4.0
✅ migrated 36 houses of data out of a possible 65 for #enpvqp
- try again with the staging but this time change the DJANGO_ALLOWED_HOSTS setting ✅ #enpvqp
#greendeploy 3. create new dockerized django project for the product database project ✅
For #greendeploy
1. work on making django-last-seen 3.2 compatible ✅
⬆️ upgraded #djangopackages to Django 4.1
5. deploy new version ✅ #enpvqp
#enpvqp 1. send Jiaqing 2 houses of data to migrate ✅
⬆️ Upgraded Django to 4.2 #djangopackages
- and deploy the newest change ✅ #enpvqp
- wrk on adding new API on VQP to allow CPOP upload of PO to auto create a similar data record in VQP's tailwind section ✅ #enpvqp
#enpvqp deploy new version