Project Info
Inspiration
I'll provide a detailed implementation plan for building this AI-enabled application using the RecipeNLG dataset, Google Cloud integrations, and GitLab’s CI/CD capabilities
What it does
The Recipe Finder application is a web-based tool designed to help users discover and manage recipes. I deployed on Google Cloud Run, it provides a scalable platform for accessing recipes anytime, anywhere How i built it I build frontend with GitLab OAuth, so i build with Google Cloud Vision API for image analysis for fastAPI Backend, and i make like dating app so its fun and engage Challenges i ran into These challenges highlight the complexity of coordinating frontend, backend, and CI/CD pipelines, especially with a new toolset like Google Cloud Build and Gitlab. Cloud Build and GitLab Integration: Setting up cloudbuild.yaml and ensuring environment variables were correctly passed from GitLab to Google Cloud Build was challenging, especially aligning the Vite VITE_ prefixes with the CI/CD process. Accomplishments that iam proud of Despite the hurdles, you’ve achieved significant milestones: Successful Deployment: The completed deployment revision on Cloud Run (with all steps—Updating service, Creating revision, Routing traffic—marked as Completed) is a major accomplishment, proving the end-to-end pipeline from code to production works. Learning Gitlab: Successfully pushing changes to a remote repository, even with initial difficulties, is a proud moment, enabling continuous deployment. What i learned Cloud Build Basics: I mastered creating and updating Cloud Build triggers, configuring cloudbuild.yaml, and monitoring builds with gcloud builds log, enhancing my CI/CD knowledge. Scalability Awareness: Deploying to Cloud Run introduced i to cloud scaling concepts, setting the stage for future optimizations.
What's next
Enhance User Experience
Analysis
View
Metric
No commits on this project resolved to a GitHub account.
Technology
- ExpressIn code
- HTMLIn code
- JavaScriptIn code
- ReactIn code
- SupabaseIn code
- Tailwind CSSIn code
- TypeScriptIn code
- CSSClaimed
7 of 8 appear in the indexed code. 1 claimed on Devpost could not be matched to code, which may simply mean the tool leaves no trace in the repository.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
20 KB
Source files
8
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
fridap251/Recipe-Finder-Meal-Planner-App
20 files · 256 KB · @ a1cfc65
Structure
Interface
1 file · 5%Screens, components and styles rendered to the user.
Application logic
6 files · 30%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- JavaScript78%
- YAML16%
- HTML3%
- TypeScript2%
- Markdown0%
Share of indexed source by file size. Binary and vendored files are excluded.
Dependencies
package.json
npm · 27- @google-cloud/logging
- @google-cloud/logging-winston
- @supabase/supabase-js
- axios
- clsx
- lucide-react
- react
- react-dom
- react-router-dom
- tailwind-merge
- winston
- +16 more
Declared in the repository’s manifests at the indexed commit. A declared package is not proof it is used, and runtime dependencies are listed first.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.