refactor: simplify migration template to support Supabase forward-only migrations

Author: ralyodio

bin/generator.js

@@ -11,7 +11,7 @@
  *
  * Server-side commands:
  * - server route: Generates a new server-side route handler
- * - server migration: Generates a new database migration file
+ * - server migration: Generates a new Supabase database migration file (forward-only)
  * - server controller: Generates a new server-side controller file
  *
  * Usage:
@@ -127,7 +127,7 @@ Client Commands:
 
 Server Commands:
   route        Generate a new server-side route handler
-  migration    Generate a new database migration file
+  migration    Generate a new Supabase database migration file (forward-only)
   controller   Generate a new server-side controller file
 
 Examples:
@@ -568,8 +568,8 @@ function generateServerMigration(args) {
     // Suggest next steps
     console.log('\nNext steps:');
     console.log('1. Edit the migration file to add your SQL commands');
-    console.log('2. Apply the migration using the appropriate command');
-    console.log('   Example: node bin/apply-migration.js');
+    console.log('2. Apply the migration using Supabase CLI or your deployment process');
+    console.log('   Note: Supabase only supports forward migrations (no DOWN methods)');
   } catch (error) {
     throw error;
   }
@@ -582,7 +582,8 @@ function showServerMigrationHelp() {
   console.log(`
 Server Migration Generator
 
-Generates a new SQL migration file with a timestamp prefix.
+Generates a new SQL migration file with a timestamp prefix for Supabase.
+Note: Supabase does not support DOWN methods, so only forward migrations are generated.
 
 Usage:
   node bin/generator.js server migration --name="add_user_fields"

templates/server/migration.sql.template

@@ -1,27 +1,12 @@
 -- Migration: {{migrationName}}
 -- Created at: {{timestamp}}
 
----------------------------------------------------------------------------
--- UP MIGRATION - Changes to apply
----------------------------------------------------------------------------
-
--- Example up migration:
+-- Example migration:
 -- CREATE TABLE new_table (
 --   id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
 --   created_at TIMESTAMPTZ NOT NULL DEFAULT NOW(),
 --   name TEXT NOT NULL
 -- );
 
--- Write your up migration SQL here:
-
-
-
----------------------------------------------------------------------------
--- DOWN MIGRATION - How to revert the changes (for rollbacks)
----------------------------------------------------------------------------
-
--- Example down migration:
--- DROP TABLE IF EXISTS new_table;
-
--- Write your down migration SQL here:
+-- Write your migration SQL here: