project details

#overview
Fund Raisers is a crowdfunding application where people can present a project, community need, or startup idea and ask others to support it. Visitors can discover active campaigns, understand why funds are needed, and contribute through an integrated payment flow. Campaign owners can publish their own requests instead of relying on a centrally curated catalog.
The project combines content, accounts, campaign state, and payments in one complete Django application. It is designed as an approachable open source implementation of the basic mechanics behind community fundraising rather than a replacement for a regulated commercial platform.
#install and run
Prepare and run
pip install -r requirements.txt
python manage.py makemigrations
python manage.py migrate
python manage.py runserver#architecture and features
Django handles routing, templates, authentication, forms, and persistence. SQLite keeps local setup small, while Bootstrap and JavaScript provide responsive presentation and interaction. Campaign models hold the funding goal, story, ownership, and progress information required by the public pages.
Razorpay supplies the payment boundary. The application creates payment intent information on the server and handles the resulting status through the configured workflow. As with any payment integration, secrets stay on the server and confirmed payment state must come from trusted provider data rather than browser input alone.
#inside the project



#using the project
- 01Clone the repository, create a Python environment, install dependencies, and configure Django plus Razorpay test credentials. Apply database migrations and create an administrative account for local management.
- 02Run the development server, register as a user, and create a campaign with its description and target. Browse campaigns from another session to verify the public discovery and detail flows.
- 03Use the payment provider's test mode to exercise a contribution without real money. Confirm successful and failed outcomes and inspect the recorded campaign progress. A production deployment would require a production database, HTTPS, verified payment callbacks, and a fuller review of financial and abuse controls.