@matrix@gameliberty.club Have you tried "npm run init" ?
@syuilo That deletes the database
@matrix@gameliberty.club "npm run init" is now alias of "npm run migrate" :)
@syuilo I tried running "npm run init" and now the database is empty
@syuilo I'm sorry. My fault. I restored my database incorrectly.
Now I'm having an issue with "npm run init"
@matrix@gameliberty.club
Please try
node built/tools/accept-migration Init 1000000000000
again. Do you get an error?
@matrix@gameliberty.club node built/tools/accept-migration Pages 1556348509290
@syuilo No error. Should I try "npm run migrate" again?
@syuilo Different error ;(
Is @u1_liquid right? https://misskey.io/notes/7uwntsg7cx
@matrix@gameliberty.club @u1_liquid@misskey.io yeah
try node built/tools/accept-migration PinnedUsers 1557476068003
@matrix@gameliberty.club @u1_liquid@misskey.io
try node built/tools/accept-migration AddSomeUrls 1557761316509
@matrix@gameliberty.club you can figure next migration that you need from here or your misskey directory/migrate
https://github.com/syuilo/misskey/tree/develop/migration
@u1_liquid @syuilo Ok, thanks. I will do that
@u1_liquid @syuilo Last 3 migrations have been executed successfully. (UserProfile1556746559567, webauthn1561706992953, ChartIndexes1561873850023)
Can I launch Misskey now?
@syuilo@misskey.io @matrix@gameliberty.club @u1_liquid@misskey.io Thanks. Misskey is working now.
@matrix@gameliberty.club it seems your database doesn't have any migration information until you running accept-migration.
I think you have to manually accept all migration that actually applied in your database.
i suggests try accept each migration files in migration folder, and try npm run migrate for each accept migration until it goes without error.
@matrix@gameliberty.club cool. try "npm run migrate" again