<@&844001800214020128> can anyone from the team sh...
# off-topic
s
@User can anyone from the team share your feedback on this?
b
As far as I understand, older projects will not automatically be migrated to 13.3, but this is something you can do by creating a new project then doing a backup and restore.
We are working on fixing some permissions issues first, then I'll be doing some testing of the procedure and I'll post a script for it.
I've done it myself, but I had to manually elevate my
postgres
user privileges temporarily, then set it back afterwards.
With the team I'll bring up the idea of doing the upgrade from the dashboard -- I'll see how feasible or desirable that might be, and if might have any possible problems.
In the meantime, I don't think there's anything in 13.3 I personally really NEED -- keep in mind 12.x is still working fine (as are all my projects still based on it) 😄
m
Definitely prefer 13!
s
but shouldn't be this done automatically for atleast paid customers?
b
Not necessarily, as it may cause issues for some people. Maybe if it's requested? I wouldn't want a host ever touching my projects unless I specifically needed them to.
s
Okay, and the user's how they will be migrated?
With the script you suggested
b
Yeah users are just a table. They migrate just fine - no changes there.
s
With passwords?
Won't the secret kye be different?
Key
b
oh yeah, that won't work
s
Social logins etc
b
I'm talking to the team about this now
s
Ok thanks
b
social logins should work
if you copy the client_ids and secrets over
but you also need to modify the callback URL in each provider because your database domain has changed with the new project
I had to do this the other day
s
Yes, correct
It says, team is working on migrating old projects. Just noticed
b
Yes, we're working on a migration path.