How lukecsharpwalker/angularblog works
Project type and purpose
• This is a full-stack, server-side rendered (SSR) blog application.
• Frontend: Angular 19 with Universal for SSR, tailwind/daisyUI for styling.
• Backend: Supabase (PostgreSQL, Auth, Storage, Functions) as a BaaS.
• CI/CD: GitHub Actions, Docker, Google Cloud Run / Firebase for deployment.
File structure
• Top-level:
• server.ts / main.server.ts: Angular Universal entry point for SSR on Node/Express.
• src/app: Angular modules split by feature (admin, auth, reader) plus shared utilities.
• app.config.server.ts vs app.config.ts: environment routing for SSR vs client.
• scripts/, .github/workflows/: automation (image conversion, CI/CD).
• public/: static assets, pre-rendered pages, tags, versioned static copies.
• Patterns:
• Feature modules for admin & reader, guarded routes for auth.
• Shared services (Supabase wrapper), stores for state (NgRX Signals).
• Utility layer (quill configuration, Supabase initializer).
README for additional insights
• Confirms Angular SSR, Supabase BaaS, Tailwind/DaisyUI, Playwright tests.
• Two distinct interfaces: Reader (public listing, details, comments) vs Admin (login, post CRUD).