backend-GPT VS supabase

Mmm, there is a real concern that even the average programmer will be replaceable quite a bit sooner than they expect. Even GPT-3 can operate as a simple application merely by being told in English how to behave. Currently this is kind of a joke, but the main constraint is memory size.

Why bother writing each backend separately? https://github.com/TheAppleTucker/backend-GPT

I saw https://github.com/TheAppleTucker/backend-GPT and decided to give this a go myself. Pretty fun stuff.

Sign up for SupaBase: Head over to SupaBase and sign up. Create a new workspace and project with your preferred names.

Setting up Supabase Create a new Supabase project, and get the connection string for the database from settings > database.

Supabase (start for free)

Built with Supabase, Astro, Unreal Speech, Stable Diffusion, Replicate, Metropolitan Museum of Art

Supabase will be used for storing article data in the database and the cover image of the article in storage. Chakra UI will be used to provide style to the elements. By using both, we can build the blog with ease.

For AutoRepurpose, I opted for Supabase as the backbone of the backend. It has reliably supported Penelope AI, which garnered over 15k users in 2022 without any issues.

Semantic search demo

1. Create a new Supabase project: Visit Supabase and create a new project.

Supabase positions itself as the "open source Firebase alternative." It was founded in 2020 and is a developer-friendly serverless database platform that supports over 20 frameworks, including popular tools like Next.js, React, Nuxt, Svelte, Flutter, and Vue.

You can find the full application code as a Python Poetry project on GitHub.