ecs-blueprints
supabase
ecs-blueprints | supabase | |
---|---|---|
2 | 768 | |
217 | 66,167 | |
1.8% | 2.4% | |
7.8 | 10.0 | |
18 days ago | 4 days ago | |
Python | TypeScript | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ecs-blueprints
- Help with the architecture of ECS Clusters with Fargate in two availability zones (with AWS)
-
Ask HN: A Better Docker Compose?
I’ve been spending a week trying to learn how to deploy a collection of containers (my web app, a Postgres DB, and some microservices) to AWS and I am still so lost.
The first solution I happened upon was serverless. Specifically SST, which is written with AWS CDK, but you must develop on live services and I just can’t justify paying to develop.
Then I found Serverless Framework, which is an abstraction on CloudFormation, but the offline solutions like localstack get a lot of flack for being buggy and localstack charges for some services. I also looked into Architect but the documentation is abysmal.
Then I figured serverful might be the easier way to go. I found that docker compose has a built in integration with AWS ECS where it transforms your yaml into Cloudformation to provision the right services. However, it seems to just be missing key parts like custom domain and SSL certificate provisioning which seems to defeat the IaC ethos.
Then I figured I might go with Terraform and I found some seemingly good starters like https://github.com/aws-ia/terraform-aws-ecs-blueprints https://github.com/cloudposse/terraform-aws-ecs-web-app https://github.com/turnerlabs/terraform-ecs-fargate but the examples are just lacking. They don’t have any examples for multiple containers that can access each others’ resources that I can find. Reading these templates has at least given me a better idea of the resources I need to provision in AWS but the networking and configuration still frighten me. Like do I need to configure nginx with a reverse proxy myself? How do I orchestrate that container with the others? And apparently services can crash and just not restart? And I need to make sure to configure volumes for data that needs to persist. And setting up the CI/CD seems daunting.
I’ve also heard about docker swarm, kubernetes, pulumi, AWS SAM, etc but it’s a lot to learn. When I go on Discords for web frameworks, mostly everyone including the devs of these frameworks use 2nd tier managed providers like Vercel, Fly, Netlify, Supabase, Cloudflare, etc. But many of those are just not as reliable as core cloud providers and the cost is way higher. Glad to see I’m not alone in a very reasonable expectation of a simple way to orchestrate multiple containers on AWS, what must be the most common use case web developers have
supabase
-
How I migrated from Firebase to Supabase
I didn't really give much thought as to which backend I would use. I already had 2 projects in Supabase (BOXCUT & MineWork), but also a few projects in Firebase too. I was more concerned at the time at actually building the product.
-
How to get free Postgres
Sign up for SupaBase: Head over to SupaBase and sign up. Create a new workspace and project with your preferred names.
-
Creating a Pokémon guessing game using Supabase, Drizzle, and Next.js in just 2 hours!
Setting up Supabase Create a new Supabase project, and get the connection string for the database from settings > database.
-
How To Make An Insanely Fast AI App (Supabase, LLAMA 3 and Groq)
Supabase (start for free)
-
Building a self-creating website with Supabase and AI
Built with Supabase, Astro, Unreal Speech, Stable Diffusion, Replicate, Metropolitan Museum of Art
-
How I built a Markdown Rendered Blog using Supabase and Chakra UI
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.
-
I got #1 Product of the Day on Product Hunt without Spending a Dollar
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.
-
AI Inference now available in Supabase Edge Functions
Semantic search demo
-
Creating an OG image using React and Netlify Edge Functions
1. Create a new Supabase project: Visit Supabase and create a new project.
-
11 Planetscale alternatives with free tiers
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.
What are some alternatives?
terraform-ecs-fargate - A Terraform template used for provisioning web application stacks on AWS ECS Fargate
Appwrite - Your backend, minus the hassle.
polycrate - Polycrate is a framework that lets you package, integrate and automate complex applications and infrastructure.
pocketbase - Open Source realtime backend in 1 file
Netmaker - Netmaker makes networks with WireGuard. Netmaker automates fast, secure, and distributed virtual networks.
nhost - The Open Source Firebase Alternative with GraphQL.
Docker Compose - Define and run multi-container applications with Docker
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
agenix - age-encrypted secrets for NixOS and Home manager
next-auth - Authentication for the Web.
Juju - Orchestration engine that enables the deployment, integration and lifecycle management of applications at any scale, on any infrastructure (Kubernetes or otherwise).
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.