Hi, Heroku and SQLite do t match. Read this: From: https://devcenter.heroku.com/articles/sqlite3
SQLite runs in memory, and backs up its data store in files on disk. While this strategy works well for development, Heroku’s Cedar stack has an ephemeral filesystem <https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem>. You can write to it, and you can read from it, but the contents will be cleared periodically. If you were to use SQLite on Heroku, you would lose your entire database at least once every 24 hours. Even if Heroku’s disks were persistent running SQLite would still not be a good fit. Since SQLite does not run as a service, each dyno would run a separate running copy. Each of these copies need their own disk backed store. This would mean that each dyno powering your app would have a different set of data since the disks are not synchronized. Em sáb., 4 de dez. de 2021 às 11:25, Rahul <gerarounak...@gmail.com> escreveu: > hey guys am using default database i.e. SQL Lite3 but when i deploy it on > heroku my static files are not getting served . Please suggest what should > i do?? > > should i use postgres ??? > > Please HELP > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/3afdbdd1-c481-498e-b659-44bfc2e691c4n%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/3afdbdd1-c481-498e-b659-44bfc2e691c4n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAMks_d16qpJN46krrGJmgPCwL943zWqsuQvfckCjtAFJVocfzA%40mail.gmail.com.
