jimmeak
commented
3 years ago Checked - but need to be updated for rebase, merge commit could be done now, but rebase has conflicts.
Closed Almad closed 3 years ago
jimmeak
commented
3 years ago Checked - but need to be updated for rebase, merge commit could be done now, but rebase has conflicts.
Almad
commented
3 years ago Looks like it's working
2021-04-28T10:10:56.400660+00:00 heroku[release.2401]: State changed from starting to up
2021-04-28T10:11:01.000000+00:00 app[api]: Build succeeded
2021-04-28T10:11:02.272860+00:00 app[release.2401]: System check identified some issues:
2021-04-28T10:11:02.272877+00:00 app[release.2401]:
2021-04-28T10:11:02.272877+00:00 app[release.2401]: WARNINGS:
2021-04-28T10:11:02.272878+00:00 app[release.2401]: ?: (mysql.W002) MySQL Strict Mode is not set for database connection 'default'
2021-04-28T10:11:02.272885+00:00 app[release.2401]: HINT: MySQL's Strict Mode fixes many data integrity problems in MySQL, such as data truncation upon insertion, by escalating warnings into errors. It is strongly recommended you activate it. See: https://docs.djangoproject.com/en/2.0/ref/databases/#mysql-sql-mode
2021-04-28T10:11:02.490384+00:00 app[release.2401]: Operations to perform:
2021-04-28T10:11:02.490386+00:00 app[release.2401]: Apply all migrations: admin, auth, contenttypes, ddcz, sessions
2021-04-28T10:11:02.725491+00:00 app[release.2401]: Running migrations:
2021-04-28T10:11:02.725497+00:00 app[release.2401]: No migrations to apply.
2021-04-28T10:11:09.072547+00:00 heroku[release.2401]: Process exited with status 0
2021-04-28T10:11:09.128445+00:00 heroku[release.2401]: State changed from up to complete
Built on top of #222