search

caproverhub / caprover-one-click-apps

Repository for Capover One Click Apps
https://caproverhub.github.io/caprover-one-click-apps/
Apache License 2.0
68 stars 36 forks source link

Tandoor Data Not Persisting #144

Closed chriskol closed 9 months ago

chriskol commented 9 months ago

Every time I restart the tandoor instance it seems like all data is lost. Not sure if this is an issue with the db not being read properly by tandoor? I haven't gone too deep but each save and restart prompts you to setup a superadmin account, space, etc. when you go to the app following

chriskol commented 9 months ago

Indeed it looks like something is up with the connection as the 'System' page on Tandoor is showing this:

Database Ok This application is not running with a Postgres database backend. This is ok but not recommended as some features only work with postgres databases.

Not sure what's up here as I can connect to the DB when making a pgadmin container and connecting with credentials

kgnfth commented 9 months ago

I will take a look at this right now.

chriskol commented 9 months ago

I've been playing around with this including trying an independent postgres install. I've seen a few issues like here that may be related but if it's a port/firewall issue, I figure I shouldn't be able to access via my pgadmin container. But this is all my starting from me being new to Oracle Cloud Infrastructure and it's admittedly been throwing me some curves as I adjust.

kgnfth commented 9 months ago

im using this cheap server from OneProvider, and even though I didn't spot any logs saying my app wasn't running PostgreSQL, I ran into a problem where the data wasn't staying persistent. Turns out, I forgot to add the environment variable DB_ENGINE=django.db.backends.postgresql. Once I added that, the data started staying persistent like it should.

I pushed the fix 0808cb0 Could you delete everything related to Tandoor in caprover and try again? or just add the env variable DB_ENGINE=django.db.backends.postgresql

chriskol commented 9 months ago

Hey it seems to be working now! That must've done it. Yeah it's tricky that it never threw any error messages. It probably could've been more direct than effectively saying "Yeah it still TECHNICALLY works but it might cause problems"