petari

Food donate Web App

https://github.com/sahil1786/petari

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (10.8%) to scientific vocabulary

Keywords from Contributors

chrome-extension contributors extension-chrome girlscriptsummerofcode2024 html-css-javascript resources
Last synced: 9 months ago · JSON representation

Repository

Food donate Web App

Basic Info
  • Host: GitHub
  • Owner: Sahil1786
  • License: other
  • Language: EJS
  • Default Branch: main
  • Homepage:
  • Size: 10.2 MB
Statistics
  • Stars: 59
  • Watchers: 2
  • Forks: 100
  • Open Issues: 66
  • Releases: 0
Created about 3 years ago · Last pushed almost 2 years ago
Metadata Files
Readme Contributing License Code of conduct

README.md

Petari - The Food Donation Management System

    **Please follow me and give a star to my repository 

🏆 Featured in:

Event Name Event Description
GirlScript Summer of Code 2024 GirlScript Summer of Code is a three-month-long Open Source Program conducted every summer by GirlScript Foundation. It is an initiative to bring more beginners to Open-Source Software Development.

Table of Contents

Introduction

PETARI, The Food Donate WebApp, is an initiative by an organization aiming to redistribute excess food from various events to those in need. The project aligns with India's Sustainable Development Goals to achieve a hunger-free world and zero food waste. By leveraging technology, PETARI seeks to bridge the gap between surplus food and hunger, thereby benefiting society and the environment.

GitHub issues GitHub forks GitHub pull requests GitHub Repo stars GitHub contributors

Tech Stack

Frontend

HTML CSS JS Bootstrap

Backend

Node.js expressjs MongoDB EJS Auth2.0

(back to top)

Features

-

Redistribution of Excess Food:

Petari focuses on collecting excess food from weddings, parties, and events to redistribute it to individuals who are hungry, thereby reducing food waste and ensuring that surplus food benefits those in need. -

Societal Impact:

The organization aims to bring benefits across society by providing access to food for individuals who may not have adequate means to access it, addressing food insecurity and hunger issues. -

Alignment with Sustainable Development Goals:

Petari's mission aligns with India's Sustainable Development Goals, particularly focusing on making the world hunger-free and reducing food waste to contribute to a sustainable and equitable society. -

Environmental Consciousness:

By redistributing excess food and reducing food waste, Petari helps alleviate the pressure on finite natural resources and minimizes the environmental impact associated with food wastage. -

Economic Impact:

Through its activities, Petari not only addresses social issues related to hunger but also contributes to economic sustainability by efficiently utilizing excess resources and reducing wastage. -

Collaboration with Events:

Petari likely collaborates with various events, such as weddings and parties, to collect surplus food, emphasizing the importance of partnerships and community involvement in achieving its goals.

(back to top)

Contribution Guidelines

Thank you for considering contributing to PETARI! We appreciate your efforts to make a positive impact on society through food redistribution and combating hunger. By contributing to PETARI, you are helping us move closer to our goal of creating a hunger-free world and reducing food waste. Please go through Contributing Guidelines.

How Can You Contribute?

There are several ways you can contribute to PETARI:

  1. Code Contributions: Help improve the PETARI codebase by fixing bugs, adding new features, or enhancing existing functionalities.

  2. Documentation: Improve the project's documentation to make it more comprehensive and user-friendly.

  3. Testing: Test the application and report any bugs or issues you encounter. You can also contribute by writing and running test cases.

  4. Design: If you have design skills, you can contribute by creating or improving the user interface and experience of PETARI.

  5. Feedback: Provide feedback on the existing features, suggest new ideas, or share your thoughts on how PETARI can be further improved.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

(back to top)

Getting Started

If you're new to contributing to open-source projects, don't worry! Here's how you can get started:

  1. Fork the Repository: Fork the PETARI repository to your GitHub account.

  2. Clone the Repository: Clone the forked repository to your local machine using Git.

    git clone https://github.com/your-username/Petari.git

  3. Open project: Open the project directory.

    cd Petari

  4. Create a new branch: To create a new branch for your profile, run the following command:

    git checkout -b add-profile

  5. Setting up Project: Once you are in the Project directory, run this command to install all necessary npm modules

    npm install

  6. Setting up dotenv file: In the Project directory, create a file named ".env". Now add the following data to it

    PORT=3000 ACCESS_TOKEN_SECRET = youraccesstokensecret MAIL_ID = yourmailid PASS_ID = your gamil app password

  7. Database: If MongoDB is not installed on your local machine, install it. Once you run the project, databases and collections will be automatically created. For installation, you can follow the installation manual given on the MongoDB website for your respective operating system:

    MongoDB Installation Manual

    Once installation is done, open your terminal:

    • If you have installed MongoDB as a service, run this command to open the MongoDB Shell:

      mongosh

- Otherwise, you can run MongoDB Community Edition from the Windows command     prompt instead of as a service. Open the command prompt, navigate to the    MongoDB directory (e.g., `C:\Program Files\MongoDB\Server\<version>\bin`),     and run this command:

    ```
    mongod
    ``` 

  This will start the MongoDB service. Don't close this terminal window     while you are working on the project. Now run this command to open the  MongoDB Shell in a new command prompt window/tab:

    ```
    mongosh  
    ```

Once MongoDB is running as a service, proceed to the next step.
  1. Running The Project On Local Machine: To run the project, navigate to the project directory. Now run the command:

    nodemon app.js

    If the above command gives an error, run this command:

    npx nodemon app.js

    Once the server starts listening, to render the webpage, go to:

    http://localhost:${PORT_MENTIONED_IN_DOTENV} or http://localhost:3000

  2. Checking Database: After running the project for the first time, databases and collections will be automatically created. To check if they are properly made, open the MongoDB Shell and run these commands:

    show dbs

    You will find a database named PetariDB. Now, run this command in the MongoDB Shell to use that database:

    use PetariDB

    To check collections inside the PetariDB, run this command in the MongoDB Shell:

    show collections

    You will see 4 collections inside the PetariDB: admins, ngos, queries, users.

  3. Make Changes: Make your desired changes to the codebase or documentation.

  4. Test Your Changes: Test your changes locally to ensure everything works as expected.

  5. Add your changed files: Add changed files to the stage by running the following command:

    git add .

  6. Commit Your Changes: Commit your changes with descriptive commit messages.

    git commit -m "message"

  7. Push Changes: Push your changes to your forked repository.

    git push

  8. Create a Pull Request: Open a pull request from your forked repository to the main PETARI repository. Provide a clear description of your changes in the pull request. Follow these steps

    • Add the issue number, that you have been assigned[Formate:- Isuue number #(your issue number)]
    • Brief description of the changes

    (back to top)

Code Style Guidelines

To maintain consistency and readability, please follow these code style guidelines:

  • Use meaningful variable and function names.
  • Follow indentation and formatting conventions used in the existing codebase.
  • Write clear and concise comments to explain complex logic or algorithms.

Code Review Process

All contributions to PETARI will go through a code review process to ensure code quality, consistency, and adherence to project standards. Your contributions are valuable, and we appreciate your patience during the review process.

Community Guidelines

PETARI is committed to fostering an inclusive and welcoming community. We encourage respectful and constructive communication among contributors. Please refer to our [Code of Conduct]-(https://github.com/Sahil1786/Petari/blob/dffa12d5f33b3227ec287af602762ef1f7bc3f89/Codeofconduct.md) for more information.

(back to top)

Output Screenshot

1. Index Page

The index page serves as the main landing page for PETARI. It showcases the mission and purpose of the organization, along with relevant information about its activities.

Index Page

2. Contact Page

This page allows users to get in touch with PETARI for inquiries, collaborations, or any other relevant communication. It provides contact information and possibly a contact form for convenience.

Contact Page

3. User Login

Users can log in to their accounts on PETARI's platform. This feature enables users to access personalized services, such as tracking their donations, managing their profiles, and more.

User Login Page

4. Admin Login

Admins have special privileges and access to manage the platform. The admin login page provides authentication for authorized personnel to perform administrative tasks, such as managing user accounts, overseeing donations, and maintaining the system.

Admin Login Page

License

This project is under LICENSE

(back to top)

Red Heart Contributors


  • This project thanking all the contributors for having your valuable contribution to our project
  • Make sure you show some love by giving ⭐ to our repository



Back to top

Owner

  • Name: SAHIL HOSSAIN
  • Login: Sahil1786
  • Kind: user
  • Location: NALHATI , WEST BENGAL

IEM || B.Tech || IT || Web Devloper

GitHub Events

Total
  • Issues event: 1
  • Watch event: 5
  • Issue comment event: 2
Last Year
  • Issues event: 1
  • Watch event: 5
  • Issue comment event: 2

Committers

Last synced: 11 months ago

All Time
  • Total Commits: 111
  • Total Committers: 29
  • Avg Commits per committer: 3.828
  • Development Distribution Score (DDS): 0.604
Past Year
  • Commits: 1
  • Committers: 1
  • Avg Commits per committer: 1.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
SAHIL HOSSAIN 1****6 44
Pankaj Kumar Bind 7****d 8
RamakrushnaBiswal r****y@g****m 7
Prateek579 p****6@g****m 6
Ananya Gupta 1****9 5
Debmalya Kuila d****2@g****m 4
Suhani Singh Paliwal 1****l 4
Heli Detroja p****7@g****m 3
Prutha p****7@g****m 3
dhananjaysingh10 i****4@g****m 3
Laxmi Pal l****7@g****m 2
Samani Humaira s****r@g****m 2
Samarth s****1@g****m 2
Vijay Shanker Sharma v****3@g****m 2
Aditya Kumar Sen 1****5 2
Abhigna Arsam 1****m 1
Anjaliavv51 1****1 1
Meet Jain 1****1 1
Naman Parashar n****5@g****m 1
Pradnya Gaitonde 1****e 1
Praveenkumar5048 p****r@g****m 1
Shadyx6 s****x@g****m 1
Sibam Paul 1****l 1
dakshsinghrathore d****9@g****m 1
harikavaleti911 1****1 1
mahek0620 1****0 1
nipun1234 n****5@g****m 1
Sanskriti Lal s****i@S****l 1
sharmi4590 b****a@g****m 1

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 75
  • Total pull requests: 60
  • Average time to close issues: 18 days
  • Average time to close pull requests: 5 days
  • Total issue authors: 48
  • Total pull request authors: 35
  • Average comments per issue: 3.35
  • Average comments per pull request: 2.42
  • Merged pull requests: 24
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 3
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 2
  • Pull request authors: 0
  • Average comments per issue: 2.0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • Sahil1786 (7)
  • Princegupta101 (6)
  • heli0707 (6)
  • Prateek579 (5)
  • Laxelspal (4)
  • suhanipaliwal (4)
  • Pruthaa17 (4)
  • RamakrushnaBiswal (4)
  • DebmalyaKuila (3)
  • Tarunag03 (3)
  • SamarthUrane (3)
  • Samani-Humaira (3)
  • thevijayshankersharma (3)
  • sreevidya-16 (2)
  • Soumya6Tiwari (2)
Pull Request Authors
  • dhananjaysingh10 (11)
  • Prateek579 (9)
  • alishasingh06 (8)
  • suhanipaliwal (7)
  • yeerekarsneha (6)
  • Laxelspal (6)
  • thevijayshankersharma (5)
  • sanayamahajan-23 (5)
  • RamakrushnaBiswal (5)
  • Prachiii8287 (4)
  • Pruthaa17 (4)
  • mahek0620 (4)
  • DebmalyaKuila (4)
  • gantasrilaitha (4)
  • Srishtiii19 (4)
Top Labels
Issue Labels
GSSOC'2024 (44) gssoc (39) good first issue (22) GSSOC'24 (22) level2 (16) documentation (11) level1 (10) enhancement (7) Level2 (5) Level1 (5) Level 1 (5) Level 3 (4) help wanted (4) bug (4) level3 (1) Level3 (1) duplicate (1)
Pull Request Labels
gssoc (58) level2 (44) GSSOC'2024 (37) GSSOC'24 (22) level1 (12) duplicate (9) good first issue (5) enhancement (4) documentation (3) invalid (2) level3 (2)