appwrite migration with external db error (1.4.13=>1.5.3) | Appwrite | Page 1

short barn Mar 12, 2024, 1:16 PM

#

Why did you delete the appwrite schema?

bold osprey Mar 12, 2024, 1:18 PM

#

In my last post, docker compose logs revealed that there wasn’t a field named factors that made appwrite console login not work, so i just deleted it, (it had no data)

unique kernel Mar 12, 2024, 2:21 PM

#

Do you have some backups? Does this have data?

bold osprey Mar 12, 2024, 2:22 PM

#

unique kernel Do you have some backups? Does this have data?

No data, i can delete it safely without any problem

#

Which I did from aws rds, created a new mariadb database

unique kernel Mar 12, 2024, 2:22 PM

#

bold osprey No data, i can delete it safely without any problem

But this is a new/clean install?

bold osprey Mar 12, 2024, 2:23 PM

#

Db on this post was old, now I have a new mariadb instance

unique kernel Mar 12, 2024, 2:23 PM

#

bold osprey Db on this post was old, now I have a new mariadb instance

I don't understand anything 😅

bold osprey Mar 12, 2024, 2:25 PM

#

The mariadb instance when I posted this (1-2 hours ago) was used for 1.4.13 then I migrated appwrite to 1.5.3. After several errors I deleted mariadb, stopped appwrite containers and created new mariadb from aws rds

#

Only 2 tables

#

Named _console__metadata and _console__metadata_perms are created

#

#

This is appwrite-maintenance

bold osprey Mar 12, 2024, 4:41 PM

#

I used the mariadb instance coming with docker-compose, it works, however with the one i created using aws rds doesn’t support it

#appwrite migration with external db error (1.4.13=>1.5.3)