Fix the encoding of a migration command.

Author: jyasskin

webserver/fly-release-command.mjs

@@ -21,4 +21,4 @@ if (process.env.FLY_APP_NAME === 'vlach-cookbook-staging') {
 
 process.env.DATABASE_URL = process.env.ADMIN_DATABASE_URL;
 console.log(execSync('prisma migrate deploy', { encoding: 'utf-8' }));
-console.log(execSync('node prisma/migrations/20240916002444_cooking_history/migrate-history-categories.mjs'), {encoding: 'utf-8'});
+console.log(execSync('node prisma/migrations/20240916002444_cooking_history/migrate-history-categories.mjs', {encoding: 'utf-8'}));

webserver/restore-prod-from-backup.mjs

@@ -30,7 +30,7 @@ process.env.DATABASE_URL = process.env.ADMIN_DATABASE_URL;
 console.log(execSync("prisma migrate deploy", { encoding: "utf-8" }));
 console.log(
   execSync(
-    "node prisma/migrations/20240916002444_cooking_history/migrate-history-categories.mjs"
-  ),
-  { encoding: "utf-8" }
+    "node prisma/migrations/20240916002444_cooking_history/migrate-history-categories.mjs",
+    { encoding: "utf-8" }
+  )
 );