⛔ #153 docs: add comprehensive AWS ECS Fargate deployment guide +49,115 -50,873 5mo ago by
amaingot ↗ analysis ↗ GitHub ## Summary
amaingot/mike-aws
A production-minded AWS edition of Mike, built by amaingot for running the full application on Amazon's cloud.
amaingot's mike-aws takes Mike in a clear operational direction: a full AWS deployment, with the services needed for sign-in, email, data, file storage, AI access, networking, and a container-based production setup.
This is not just an infrastructure sketch. The fork pairs its AWS deployment story with stronger pull-request checks across the frontend and backend, suggesting an effort to make the platform easier to operate and safer to change. Curious readers can follow the implementation details on GitHub.
What's in it
- Full AWS deployment A production architecture covering networking, identity, email, database, storage, AI access, DNS, certificates, secrets, permissions, and container hosting.
- AWS-based AI access Model access is part of the AWS deployment plan, placing the application's AI capability within the same cloud platform.
- Production operations The deployment approach accounts for the practical pieces of running a live service, from IAM and secrets to DNS and certificates.
- Stronger change checks Pull requests are being given separate formatting, linting, type-checking, build, and migration safeguards across the application.
Direction
infrastructuresecurityworkflow
Activity
⛔ #152 ci: add typecheck, lint, and format checks to PR workflow +47,966 -50,873 5mo ago by
amaingot ↗ analysis ↗ GitHub ## Summary
The fork has quietly re-platformed off Cloudflare and Supabase onto Amazon's cloud, and a routine housekeeping pull request accidentally put the whole rebuild on display.
One sweeping move ports the entire stack off Cloudflare and Supabase and onto Amazon's cloud - login, data, file storage, and the AI itself.
Threads of work (detailed view)
amaingot moves Mike's whole stack onto AWS
The fork has quietly re-platformed off Cloudflare and Supabase onto Amazon's cloud, and a routine housekeeping pull request accidentally put the whole rebuild on display.
amaingot rebuilds Mike on AWS, top to bottom
One sweeping move ports the entire stack off Cloudflare and Supabase and onto Amazon's cloud - login, data, file storage, and the AI itself.
Full AWS re-platform: Cognito auth, Drizzle ORM, S3, Bedrock, Docker compose stack
amaingot lands a 64-file, ~16k-line commit that swaps every Cloudflare/Supabase dependency for AWS: Cognito for auth, RDS Postgres via Drizzle for data, S3 for storage, Bedrock for Claude. A full local dev stack (MinIO, cognito-local, smtp4dev) comes with it via docker-compose. This is the fork's defining change.
Pull requests (detailed view)
⛔ Closed without merge (2)
by
amaingot · opened 5mo ago · closed 5mo ago by
amaingot · opened 5mo ago · closed 5mo ago