Repository navigation
feat: containerize API and add database options - #56
procoder-ji merged 3 commits into
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
procoder-ji
left a comment
procoder-ji
left a comment
There was a problem hiding this comment.
Thanks @Coding-Professional for the container setup and database options. Reviewed the current implementation and Neon follow-up; no blocking changes requested.
Checked account identity/isolation, transaction retries, SQL Server migrations and snapshots, Mongo progress generation/revision checks, durable Data Protection keys, Docker/Compose, and CI. Neon correctly uses Production with a pooled runtime connection and a direct migration connection. The focused relational/account tests pass (8/8), and the Neon Compose configuration validates.
Three CI checks are green at review time; browser/SEO is still running. Live Neon connectivity, Vercel deployment and Google consent remain the documented operator verification steps.
Containerize the ASP.NET Core API with PostgreSQL, SQL Server, or MongoDB. Neon PostgreSQL is the selected hosted setup, with pooled runtime and direct migration connections. Includes persistent Compose stacks, an optional Vercel backend config, and contributor documentation.
Validated API contracts against SQLite and all three servers, Compose startup/restart persistence, locked restore, and image smoke. Neon Compose configuration and Npgsql connection settings also validate. Live Neon/Vercel deployment requires operator credentials and has not been performed.