To me this looks like a path / environment issue.
Okay but why should django try to use SQLite? Or isnât it trying to use it? But why shouldnât it find the tables then?
Because itâs the default.
Because no database has been initialised.
Wouldnât that mean seahub_settings.py is ingored? What could be a solution?
Anything to watch out for when upgrading to Debian Stretch?
Keep in mind that they switched from MySQL to MariaDB as the default MySQL server. In theory, the upgrade should work without problems but you canât be 100% sure before noticing the changes. See https://mariadb.com/kb/en/mariadb/moving-from-mysql-to-mariadb-in-debian-9/
I use MariaDB since itâs stable already, so nothing to change here. ![]()
No issues upgrading to Stretch, including switch to systemd, Docker LE etcâŚ