Co-OpFlow: Project Story

Inspiration

Co-OpFlow was inspired by the need for a unified platform where innovators, hackers, and creators can easily find teammates, collaborate on projects, and build ideas together. We wanted to streamline the process of forming teams, sharing knowledge, and launching new ventures, especially for hackathons and startup communities.

What it does

Co-OpFlow connects users with projects, teams, and community spaces. It enables:

Account creation and profile management
Project and team exploration
Collaboration through forums and events
Messaging and notifications
Project interactions (likes, uploads, details)

How we built it

The backend uses FastAPI and MongoDB for robust, async APIs and data storage. JWT authentication secures user actions. The frontend is built with React and Tailwind CSS, providing a modern, responsive UI. State management is handled by Zustand, and API communication is streamlined via custom hooks and services.

Challenges we ran into

Database issues: Integrating MongoDB with async drivers and ensuring smooth startup/shutdown in Docker Compose required careful orchestration. Mocking database calls for tests was tricky, especially for authentication and messaging flows.
Dependency problems: We faced compatibility issues between passlib and bcrypt, leading to registration errors and warnings. Pinning the correct bcrypt version in requirements.txt resolved this. Managing dependencies in Docker builds and local environments was a recurring challenge.
Environment mismatches: Differences between local development, Docker containers, and CI environments often caused unexpected bugs, especially with Python versions and package installations.
Testing async code: Writing reliable tests for async endpoints and database operations required special fixtures and careful mocking, which is a common pain point in modern Python projects.
CORS and API connectivity: Ensuring the frontend could reliably connect to the backend, especially with CORS settings and environment variables, was a frequent source of confusion.
Frontend state bugs: Managing authentication state and API errors in React, especially with async flows and Zustand, led to subtle bugs and required careful debugging.
File uploads and static assets: Handling uploads and serving static files in development and production environments was more complex than expected, especially with Docker and local paths.