UN-101: Migrate database to Turso and Libsql

[damiensedgwick]

Migration from Vercel/PostgreSQL to Turso/LibSQL

Overview

This PR implements a significant infrastructure change, moving our database from Vercel's PostgreSQL to Turso's LibSQL. This migration offers several advantages:

1. Increased storage capacity
2. Elimination of bandwidth restrictions
3. Potential for improved performance and scalability

Implementation Details

• Followed the Turso documentation for integration with Drizzle ORM
• Updated database configuration and connection logic
• Modified queries and schema definitions to ensure SQLite compatibility

Configuration Notes

• Current database configuration points to .env.local
• For production deployment, this should be updated to use .env

Database Ownership

• The Turso database is currently set up under a personal account
• Action Item: Establish a team account or organization-level ownership for the database

Next Steps

1. Review and test all database interactions to ensure full compatibility
2. Update deployment scripts and environment variables for production
3. Set up a team account on Turso and migrate the database ownership
4. Update documentation to reflect the new database setup and any changed procedures

Additional Considerations

• Verify backup and restore procedures for the new database
• Assess any impacts on application performance and optimize if necessary
• Consider implementing database migration scripts for smooth transitions in the future

Please review these changes carefully, particularly focusing on SQLite-specific adaptations and any performance implications.

[linear]

UN-101 Move over to Tursoooo

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
atproto-browser	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 30, 2024 8:53pm
frontpage	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 30, 2024 8:53pm

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
unravel	⬜️ Ignored (Inspect)	Visit Preview		Aug 30, 2024 8:53pm

[damiensedgwick]

Most of the grunt work has been done. schema.ts has been migrated to sqlite syntax. For some of the properties, there was not a direct migration such as serial for postgres, this is just an integer and there is no timestamp / date column for drizzle + sqlite so this is just a text field.

New migrations were generated and pushed to turso with no issues but there is still work to do where there is now some type incompatibilities.

[damiensedgwick]

transaction files have been migrated to sqlite syntax also now, pr needs to be tested at this point, posts created / selected etc, same for comments. I am unable to login to the app at the moment so I cannot test this myself.

[damiensedgwick]

Bigint does not exist in sqlite but I noticed this was used for the consumed offsets, sqlite integers have a max value of 263 - 1 == 9223372036854775807 so I figure this should be fine.

[damiensedgwick]

Fix this: frontpage:build: Type error: Type 'string' is not assignable to type 'Date'.