MySQL8 External DB: SQLSTATE[42000]: Syntax error or access violation: 1064
Did you do that yet?
Yes. But it doesnβt seems to work, I tried placing just mysql, but reading the code further the line, I think I need to place a connection string. I will try that next
should work, as it creates a DSN
ok, so the way that one works it's a bit weird because it's not meant completely to work that way but like a 'patched' way lol
it should have someting={Connection String}
so, to follow the same format as the fallbackForDB variable which is the one that creates the 'mariadb' connection I added db_main= before
So in order to have it for posterity:
_APP_CONNECTIONS_DB_CONSOLE=db_main=mysql://user:password@mysqlhost:port/database_name
_APP_CONNECTIONS_DB_PROJECT=db_main=mysql://user:password@mysqlhost:port/database_name
all good now <:appwritemandancing:946072376079188039>
How can I update to 1.4.7 manually? So my .env won't change?
what's wrong with changing your .env file?
Well, not only my env, also my docker-compose.yml, it has all the entries for the db connection, if I run de the upgrade entrypoint it will change that docker-compose file and the env, right?
I was just wondering if there is a way to upgrade without that entrypoint
uhhhhhhhh the best thing to do is to keep the docker-compose.yml file generated by Appwrite as untouched as possible and put your customizations in a docker-compose.override.yml file
yes, upgrade will essentially wipe the docker-compose.yml file. the .env may be updated as well, but old values should retain
Yeah, just tested it and it deletes my old env vars, the db connection string, I'll try bumping up the image versions tho, if that's the only thing that has changed from 1.4.6
You should be putting env vars in the .env file, not the docker compose file.
I highly discourage manually upgrading because who knows what you might miss
I place those on my env file
I will compare the work that has to be done, like recreating my docker-compose file,
Thanks
and again, i highly encourage using a docker-compose.override.yml file as much as you can
Yes, I agree, thanks
I did two servers upgrades with different approaches to know the differences, both worked the same
the upgrade from 1.4.6 to 1.4.7 was very minor (just the version bump), but there are other times where the change is much bigger. in those cases, you really don't want to miss things
For sure, with that in mind, I was testing some other things that we can do like horizontal scaling
