To create a migration, you only need two commands: - supabase migration new <migration_name> - supabase migration up --db-url <database_connection_string> <database_connection_string - for local development this is usual 'postgresql://postgres:[email protected]:54322/postgres' Prerequisites: You need to have the Supabase CLI installed and run it from within a local Supabase project.

Hello engineers, I have added on Github new things in the FarmAssistant: - NextJs frontend client - A migration in Supabase backend Next.js is a basic template—I haven't made any changes to it yet. The Supabase migration adds multi-tenancy support, which will be useful later.

Hello engineers, I've created a project I'll be working on, and I'll track my progress here in the group. It's an open-source farm management app. I'll share updates here and answer any questions about the project. Github for the reference - https://github.com/Karol-Szykula/FarmAssistant The stack: - Nextjs - Supabase First steps ✅ - Created a monorepo - Contains two directories: client/ and server/ - server/ includes the Supabase project - Both server/ and client/ have their own package.json files Next steps 🔄 - Create initial migration with multitenancy (tenants table + RLS) - Set up Next.js project in the client/ directory Stay tuned for the first migration SQL and Next.js setup! 🚜

Hi, i pasted below screen about my compositon of frontend project. I use in one package .html .css .js. Then with loader existing in each package i mount and load into app.jsx where is root-container. Is this type of front-end project structure common in commercial projects? Tech stack: Java, JavaScript, PostgreSQL

On Ubuntu /etc/libvirt/qemu/redhat-amd64.xml