├── .dockerignore
├── .env.example
├── .eslintrc.json
├── .github
├── ISSUE_TEMPLATE
│ ├── bug.yml
│ ├── docs.yml
│ ├── feature.yml
│ └── styles.yml
├── deploy.yml
├── pull_request_template.md
└── workflows
│ ├── autocomment-iss-close.yml
│ ├── close-old-issue.yml
│ ├── close-old-pr.yml
│ ├── close-on-merge.yml
│ ├── issue-created.yml
│ └── pull_request_created.yml
├── .gitignore
├── .vscode
└── settings.json
├── CODE_OF_CONDUCT.md
├── Dockerfile
├── LICENSE
├── README.md
├── asset
├── 404.jpg
├── Header.png
├── LogIn.png
├── avatar.png
├── blood.svg
├── blood3.png
├── clerk.png
├── donor.jpg
├── heartbeat.svg
└── pencil.svg
├── components.json
├── contributing.md
├── docker-compose.yml
├── next.config.mjs
├── package-lock.json
├── package.json
├── postcss.config.js
├── prisma
└── schema.prisma
├── public
├── next.svg
└── vercel.svg
├── src
├── Content
│ └── State.json
├── Context
│ └── ThemeContext.tsx
├── app
│ ├── DonorForm
│ │ └── page.tsx
│ ├── FindBlood
│ │ └── page.tsx
│ ├── OrgForm
│ │ └── page.tsx
│ ├── ThankYou
│ │ └── page.tsx
│ ├── api
│ │ ├── DonorForm
│ │ │ └── route.ts
│ │ └── orgForm
│ │ │ └── route.ts
│ ├── favicon.ico
│ ├── globals.css
│ ├── layout.tsx
│ ├── libs
│ │ └── prismadb.ts
│ ├── loading.tsx
│ ├── not-found.tsx
│ ├── page.tsx
│ ├── sign-in
│ │ └── [[...sign-in]]
│ │ │ └── page.tsx
│ └── sign-up
│ │ └── [[...sign-up]]
│ │ └── page.tsx
├── components
│ ├── BloodGroupFilter.tsx
│ ├── Dashboard.jsx
│ ├── DonorCard.tsx
│ ├── Footer.tsx
│ ├── GetBlood.tsx
│ ├── Hero.tsx
│ ├── Loading.tsx
│ ├── Navbar.tsx
│ ├── OurMission.tsx
│ ├── ScrollToTopButton.tsx
│ ├── ThemeToggler.tsx
│ └── ui
│ │ ├── alert.tsx
│ │ ├── border-beam.tsx
│ │ ├── button.tsx
│ │ ├── dropdown-menu.tsx
│ │ ├── input.tsx
│ │ ├── label.tsx
│ │ ├── separator.tsx
│ │ └── shiny-button.tsx
├── lib
│ └── utils.ts
├── middleware.ts
└── utils
│ └── cn.ts
├── tailwind.config.ts
├── tf
└── main.tf
└── tsconfig.json
/.dockerignore:
--------------------------------------------------------------------------------
1 | # Ignore node modules
2 | node_modules
3 |
4 | # Ignore log files
5 | *.log
6 |
7 | # Ignore build output
8 | build
9 | dist
10 |
11 | # Ignore dotenv files (secrets and environment variables)
12 | .env
13 | .env.local
14 | .env.development.local
15 | .env.test.local
16 | .env.production.local
17 |
18 |
19 | # Ignore any files related to git
20 | .git
21 | .gitignore
22 |
23 | # Ignore miscellaneous files
24 | .DS_Store
25 | *.swp
26 | .github
27 | .git
28 | .gitignore
29 | CODE_OF_CONDUCT.md
30 | README.md
31 | contributing.md
32 |
--------------------------------------------------------------------------------
/.env.example:
--------------------------------------------------------------------------------
1 | NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=
2 | CLERK_SECRET_KEY=
3 | NEXT_PUBLIC_CLERK_SIGN_IN_URL=/sign-in
4 | NEXT_PUBLIC_CLERK_SIGN_UP_URL=/sign-up
5 | NEXT_PUBLIC_CLERK_AFTER_SIGN_IN_URL=/
6 | NEXT_PUBLIC_CLERK_AFTER_SIGN_UP_URL=/
7 | DATABASE_URL="PUT MONGODB URI"
8 |
--------------------------------------------------------------------------------
/.eslintrc.json:
--------------------------------------------------------------------------------
1 | {
2 | "extends": "next/core-web-vitals"
3 | }
4 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/bug.yml:
--------------------------------------------------------------------------------
1 | name: 🐞 Bug Report
2 | description: File a bug report
3 | title: "Bug: "
4 | labels: ["🛠 goal: fix", "🚦status: awaiting triage", "💻 aspect: code"]
5 | body:
6 | - type: textarea
7 | id: what-happened
8 | attributes:
9 | label: What happened?
10 | placeholder: Add descriptions
11 | validations:
12 | required: true
13 | - type: textarea
14 | id: screenshots
15 | attributes:
16 | label: Add screenshots
17 | placeholder: Add screenshots
18 | validations:
19 | required: true
20 | - type: dropdown
21 | id: browsers
22 | attributes:
23 | label: What browsers are you seeing the problem on?
24 | multiple: true
25 | options:
26 | - Firefox
27 | - Chrome
28 | - Safari
29 | - Microsoft Edge
30 | - Brave
31 | - Other
32 | - type: checkboxes
33 | id: terms
34 | attributes:
35 | label: "Record"
36 | options:
37 | - label: I have checked the existing [issues](https://github.com/Saurav-Pant/Blood-Donation-Project/issues)
38 | required: true
39 |
40 | - label: I have read the [Contributing Guidelines](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/contributing.md)
41 | required: true
42 |
43 | - label: I agree to follow this project's [Code of Conduct](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/CODE_OF_CONDUCT.md)
44 | required: true
45 |
46 | - label: I want to work on this issue
47 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/docs.yml:
--------------------------------------------------------------------------------
1 | name: 🔖 Documentation update
2 | description: Improve Documentation
3 | title: "docs:"
4 | labels:
5 | [
6 | "📄 aspect: text",
7 | "🚦status: awaiting triage",
8 | "✨ goal: improvement",
9 | "good first issue",
10 | "🟨 priority: medium",
11 | ]
12 | body:
13 | - type: textarea
14 | id: improve-docs
15 | attributes:
16 | label: what's wrong with the documentation?
17 | description: which things do we need to add?
18 | placeholder: Add description
19 | validations:
20 | required: true
21 | - type: textarea
22 | id: screenshots
23 | attributes:
24 | label: Add screenshots
25 | description: Add screenshots to see the demo
26 | placeholder: Add screenshots
27 | validations:
28 | required: true
29 | - type: checkboxes
30 | id: terms
31 | attributes:
32 | label: "Record"
33 | options:
34 | - label: I have checked the existing [issues](https://github.com/Saurav-Pant/Blood-Donation-Project/ProjectsHut/issues)
35 | required: true
36 |
37 | - label: I have read the [Contributing Guidelines](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/contributing.md)
38 | required: true
39 |
40 | - label: I agree to follow this project's [Code of Conduct](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/CODE_OF_CONDUCT.md)
41 | required: true
42 |
43 |
44 |
45 | - label: I want to work on this issue
46 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/feature.yml:
--------------------------------------------------------------------------------
1 | name: ✨ Feature Request
2 | description: Suggest a feature request
3 | title: "feat:"
4 | labels: ["⭐ goal: addition", "🚦status: awaiting triage"]
5 | body:
6 | - type: textarea
7 | id: what-feature
8 | attributes:
9 | label: What feature?
10 | placeholder: Add descriptions
11 | validations:
12 | required: true
13 | - type: textarea
14 | id: screenshots
15 | attributes:
16 | label: Add screenshots
17 | placeholder: Add screenshots
18 | validations:
19 | required: true
20 | - type: checkboxes
21 | id: terms
22 | attributes:
23 | label: "Record"
24 | options:
25 | - label: I have checked the existing [issues](https://github.com/Saurav-Pant/Blood-Donation-Project/issues)
26 | required: true
27 |
28 | - label: I have read the [Contributing Guidelines](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/contributing.md)
29 | required: true
30 |
31 | - label: I agree to follow this project's [Code of Conduct](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/CODE_OF_CONDUCT.md)
32 | required: true
33 |
34 |
35 |
36 | - label: I want to work on this issue
37 |
--------------------------------------------------------------------------------
/.github/ISSUE_TEMPLATE/styles.yml:
--------------------------------------------------------------------------------
1 | name: 👯♂️ Style Changing Request
2 | description: Suggest a style design
3 | title: '[style]: '
4 | labels: ["✨ goal: improvement","🚦status: awaiting triage","🕹 aspect: interface"]
5 | body:
6 | - type: markdown
7 | attributes:
8 | value: |
9 | Thanks for taking the time to fill out this template!
10 | - type: textarea
11 | id: style-idea
12 | attributes:
13 | label: What's the style idea?
14 | placeholder: Add descriptions
15 |
16 | validations:
17 | required: true
18 | - type: textarea
19 | id: screenshots
20 | attributes:
21 | label: Add screenshots
22 |
23 | placeholder: Add screenshots
24 |
25 | - type: checkboxes
26 | id: terms
27 | attributes:
28 | label: "Record"
29 |
30 | options:
31 | - label: I have checked the existing [issues](https://github.com/Saurav-Pant/Blood-Donation-Project/issues)
32 | required: true
33 |
34 | - label: I have read the [Contributing Guidelines](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/contributing.md)
35 | required: true
36 |
37 | - label: I agree to follow this project's [Code of Conduct](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/CODE_OF_CONDUCT.md)
38 | required: true
39 |
40 |
41 |
42 | - label: I want to work on this issue
43 |
44 |
--------------------------------------------------------------------------------
/.github/deploy.yml:
--------------------------------------------------------------------------------
1 | name: CI/CD to EC2
2 |
3 | on:
4 | push:
5 | branches: [ main ]
6 |
7 | jobs:
8 | deploy:
9 | runs-on: ubuntu-latest
10 |
11 | steps:
12 | - uses: actions/checkout@v2
13 |
14 | - name: Install Node.js
15 | uses: actions/setup-node@v2
16 | with:
17 | node-version: '14'
18 |
19 | - name: Install dependencies
20 | run: npm ci
21 |
22 | - name: Build
23 | run: npm run build
24 |
25 | - name: Deploy to EC2
26 | env:
27 | PRIVATE_KEY: ${{ secrets.EC2_SSH_PRIVATE_KEY }}
28 | HOST: ${{ secrets.EC2_HOST }}
29 | USER: ec2-user
30 | run: |
31 | echo "$PRIVATE_KEY" > private_key && chmod 600 private_key
32 | scp -i private_key -o StrictHostKeyChecking=no -r .next package.json package-lock.json ${USER}@${HOST}:/var/www/nextjs/
33 | ssh -i private_key -o StrictHostKeyChecking=no ${USER}@${HOST} '
34 | cd /var/www/nextjs
35 | npm ci
36 | pm2 restart nextjs || pm2 start npm --name "nextjs" -- start
37 | '
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 | ## Related Issue
2 | [Cite any related issue(s) this pull request addresses. If none, simply state "None”]
3 |
4 | ## Description
5 | [Please include a brief description of the changes or features added]
6 |
7 | ## Type of PR
8 |
9 | - [ ] Bug fix
10 | - [ ] Feature enhancement
11 | - [ ] Documentation update
12 | - [ ] Other (specify): _______________
13 |
14 | ## Screenshots / videos (if applicable)
15 | [Attach any relevant screenshots or videos demonstrating the changes]
16 |
17 | ## Checklist:
18 | - [ ] I have performed a self-review of my code
19 | - [ ] I have read and followed the Contribution Guidelines.
20 | - [ ] I have tested the changes thoroughly before submitting this pull request.
21 | - [ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
22 | - [ ] I have commented my code, particularly in hard-to-understand areas.
23 |
24 |
25 | ## Additional context:
26 | [Include any additional information or context that might be helpful for reviewers.]
27 |
--------------------------------------------------------------------------------
/.github/workflows/autocomment-iss-close.yml:
--------------------------------------------------------------------------------
1 | name: Comment on Issue Close
2 |
3 | on:
4 | issues:
5 | types: [closed]
6 |
7 | jobs:
8 | greet-on-close:
9 | runs-on: ubuntu-latest
10 | permissions:
11 | issues: write
12 | steps:
13 | - name: Greet User
14 | uses: actions/github-script@v5
15 | with:
16 | github-token: ${{ secrets.GITHUB_TOKEN }}
17 | script: |
18 | const issue = context.payload.issue;
19 | const issueCreator = issue.user.login;
20 | const issueNumber = issue.number;
21 |
22 | const greetingMessage = `Hello @${issueCreator}! Your issue #${issueNumber} has been closed. Thank you for your contribution!`;
23 |
24 | github.rest.issues.createComment({
25 | owner: context.repo.owner,
26 | repo: context.repo.repo,
27 | issue_number: issueNumber,
28 | body: greetingMessage
29 | });
--------------------------------------------------------------------------------
/.github/workflows/close-old-issue.yml:
--------------------------------------------------------------------------------
1 | name: Close Old Issues
2 | on:
3 | schedule:
4 | - cron: "0 0 * * *"
5 |
6 | jobs:
7 | close-issues:
8 | runs-on: ubuntu-latest
9 |
10 | steps:
11 | - name: Checkout Repository
12 | uses: actions/checkout@v4
13 |
14 | - name: Close Old Issues
15 | run: |
16 | open_issues=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
17 | "https://api.github.com/repos/${{ github.repository }}/issues?state=open" \
18 | | jq -r '.[] | .number')
19 | for issue in $open_issues; do
20 | # Get the last updated timestamp of the issue
21 | last_updated=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
22 | "https://api.github.com/repos/${{ github.repository }}/issues/$issue" \
23 | | jq -r '.updated_at')
24 | days_since_update=$(( ( $(date +%s) - $(date -d "$last_updated" +%s) ) / 86400 ))
25 | if [ $days_since_update -gt 30 ]; then
26 | curl -s -X PATCH -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
27 | -H "Accept: application/vnd.github.v3+json" \
28 | -d '{"state":"closed"}' \
29 | "https://api.github.com/repos/${{ github.repository }}/issues/$issue"
30 |
31 | # Add a comment explaining when the issue will be closed
32 | curl -s -X POST -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
33 | -H "Accept: application/vnd.github.v3+json" \
34 | -d '{"body":"This issue has been automatically closed because it has been inactive for more than 30 days. If you believe this is still relevant, feel free to reopen it or create a new one. Thank you!"}' \
35 | "https://api.github.com/repos/${{ github.repository }}/issues/$issue/comments"
36 | fi
37 | done
--------------------------------------------------------------------------------
/.github/workflows/close-old-pr.yml:
--------------------------------------------------------------------------------
1 | name: Close Stale PRs
2 |
3 | on:
4 | schedule:
5 | - cron: '0 0 * * *' # Runs daily at midnight
6 | pull_request:
7 | types:
8 | - opened
9 | - reopened
10 | - synchronize
11 |
12 | permissions:
13 | pull-requests: write
14 | issues: write
15 |
16 | jobs:
17 | close_stale_prs:
18 | runs-on: ubuntu-latest
19 | permissions:
20 | pull-requests: write
21 |
22 | steps:
23 | - uses: actions/stale@v7
24 | with:
25 | repo-token: ${{ secrets.GITHUB_TOKEN }}
26 | stale-pr-message: 'This PR has been automatically closed due to inactivity from the owner for 90 days.'
27 | days-before-pr-stale: 90
28 | days-before-pr-close: 0
29 | exempt-pr-author: false
30 | exempt-pr-labels: ''
31 | only-labels: ''
32 | operations-per-run: 30
33 | remove-stale-when-updated: true
34 | debug-only: false
35 |
--------------------------------------------------------------------------------
/.github/workflows/close-on-merge.yml:
--------------------------------------------------------------------------------
1 | name: Close Issues on PR Merge
2 |
3 | on:
4 | pull_request:
5 | types: [closed]
6 |
7 | jobs:
8 | close-issues:
9 | runs-on: ubuntu-latest
10 |
11 | steps:
12 | - name: Checkout repository
13 | uses: actions/checkout@v2
14 |
15 | - name: Close linked issues
16 | if: github.event.pull_request.merged == true
17 | run: |
18 | ISSUES=$(jq -r '.pull_request.body' "$GITHUB_EVENT_PATH" | grep -Eo '#[0-9]+' | tr -d '#')
19 | for ISSUE in $ISSUES
20 | do
21 | echo "Closing issue #$ISSUE"
22 | curl -X POST -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
23 | -H "Accept: application/vnd.github.v3+json" \
24 | https://api.github.com/repos/${{ github.repository }}/issues/$ISSUE/comments \
25 | -d '{"body":"Closed by PR #${{ github.event.pull_request.number }}"}'
26 | curl -X PATCH -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
27 | -H "Accept: application/vnd.github.v3+json" \
28 | https://api.github.com/repos/${{ github.repository }}/issues/$ISSUE \
29 | -d '{"state":"closed"}'
30 | done
--------------------------------------------------------------------------------
/.github/workflows/issue-created.yml:
--------------------------------------------------------------------------------
1 | name: Greet New Contributors
2 |
3 | on:
4 | issues:
5 | types: [opened]
6 |
7 | permissions:
8 | contents: read
9 | issues: write
10 |
11 | jobs:
12 | greet:
13 | runs-on: ubuntu-latest
14 | steps:
15 | - name: Checkout code
16 | uses: actions/checkout@v2
17 |
18 | - name: Greet the contributor
19 | uses: actions/github-script@v6
20 | with:
21 | script: |
22 | const issue_number = context.issue.number;
23 | const owner = context.repo.owner;
24 | const repo = context.repo.repo;
25 | github.rest.issues.createComment({
26 | issue_number: issue_number,
27 | owner: owner,
28 | repo: repo,
29 | body: 'Thank you for opening an issue! We will look into it ASAP. star the repo if you like it.'
30 | });
31 |
--------------------------------------------------------------------------------
/.github/workflows/pull_request_created.yml:
--------------------------------------------------------------------------------
1 | name: Greet New Pull Request
2 |
3 | on:
4 | pull_request:
5 | types: [opened]
6 |
7 | permissions:
8 | contents: read
9 | pull-requests: write
10 |
11 | jobs:
12 | greet:
13 | runs-on: ubuntu-latest
14 | steps:
15 | - name: Checkout code
16 | uses: actions/checkout@v2
17 |
18 | - name: Greet the contributor
19 | uses: actions/github-script@v6
20 | with:
21 | github-token: ${{ secrets.GITHUB_TOKEN }}
22 | script: |
23 | const pr_number = context.issue.number;
24 | const owner = context.repo.owner;
25 | const repo = context.repo.repo;
26 | github.rest.issues.createComment({
27 | issue_number: pr_number,
28 | owner: owner,
29 | repo: repo,
30 | body: 'Thank you for submitting this pull request! We appreciate your contribution.'
31 | });
32 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | /node_modules
2 | /.pnp
3 | .pnp.js
4 | .yarn/install-state.gz
5 |
6 | # testing
7 | /coverage
8 |
9 | # next.js
10 | /.next/
11 | /out/
12 |
13 | # production
14 | /build
15 |
16 | # misc
17 | .DS_Store
18 | *.pem
19 |
20 | # debug
21 | npm-debug.log*
22 | yarn-debug.log*
23 | yarn-error.log*
24 |
25 | # local env files
26 | .env*.local
27 | .env
28 |
29 | # vercel
30 | .vercel
31 |
32 | # typescript
33 | *.tsbuildinfo
34 | next-env.d.ts
35 |
--------------------------------------------------------------------------------
/.vscode/settings.json:
--------------------------------------------------------------------------------
1 | {
2 | "WillLuke.nextjs.hasPrompted": true
3 | }
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | - Demonstrating empathy and kindness toward other people
21 | - Being respectful of differing opinions, viewpoints, and experiences
22 | - Giving and gracefully accepting constructive feedback
23 | - Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | - Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | - The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | - Trolling, insulting or derogatory comments, and personal or political attacks
33 | - Public or private harassment
34 | - Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | - Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at [Saurav Pant](https://twitter.com/Saurav-Pant)
63 | All complaints will be reviewed and investigated promptly and fairly.
64 |
65 | All community leaders are obligated to respect the privacy and security of the
66 | reporter of any incident.
67 |
68 | ## Enforcement Guidelines
69 |
70 | Community leaders will follow these Community Impact Guidelines in determining
71 | the consequences for any action they deem in violation of this Code of Conduct:
72 |
73 | ### 1. Correction
74 |
75 | **Community Impact**: Use of inappropriate language or other behavior deemed
76 | unprofessional or unwelcome in the community.
77 |
78 | **Consequence**: A private, written warning from community leaders, providing
79 | clarity around the nature of the violation and an explanation of why the
80 | behavior was inappropriate. A public apology may be requested.
81 |
82 | ### 2. Warning
83 |
84 | **Community Impact**: A violation through a single incident or series
85 | of actions.
86 |
87 | **Consequence**: A warning with consequences for continued behavior. No
88 | interaction with the people involved, including unsolicited interaction with
89 | those enforcing the Code of Conduct, for a specified period of time. This
90 | includes avoiding interactions in community spaces as well as external channels
91 | like social media. Violating these terms may lead to a temporary or
92 | permanent ban.
93 |
94 | ### 3. Temporary Ban
95 |
96 | **Community Impact**: A serious violation of community standards, including
97 | sustained inappropriate behavior.
98 |
99 | **Consequence**: A temporary ban from any sort of interaction or public
100 | communication with the community for a specified period of time. No public or
101 | private interaction with the people involved, including unsolicited interaction
102 | with those enforcing the Code of Conduct, is allowed during this period.
103 | Violating these terms may lead to a permanent ban.
104 |
105 | ### 4. Permanent Ban
106 |
107 | **Community Impact**: Demonstrating a pattern of violation of community
108 | standards, including sustained inappropriate behavior, harassment of an
109 | individual, or aggression toward or disparagement of classes of individuals.
110 |
111 | **Consequence**: A permanent ban from any sort of public interaction within
112 | the community.
113 |
--------------------------------------------------------------------------------
/Dockerfile:
--------------------------------------------------------------------------------
1 | FROM node:20-alpine
2 |
3 | WORKDIR /usr/app
4 |
5 | COPY package.json package-lock.json ./
6 | RUN npm ci && npm i sharp
7 |
8 | COPY prisma ./prisma
9 | COPY . .
10 |
11 | RUN npx prisma generate
12 | RUN npm run build || true
13 |
14 | EXPOSE 3000
15 |
16 | CMD ["npm", "run", "start"]
17 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2024 Saurav Pant
4 |
5 | Permission is hereby granted, free of charge, to any person obtaining a copy
6 | of this software and associated documentation files (the "Software"), to deal
7 | in the Software without restriction, including without limitation the rights
8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 |
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 |
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 |
Blood Donation
2 | Welcome 👋
3 |
4 |
5 | The Blood Donation Project is an initiative aimed at connecting individuals in need of blood with willing blood donors. The project utilizes npm (Node Package Manager) and version control using Git to manage the codebase and facilitate collaboration.
6 |
7 |
8 | ## 💻 Tech Stack
9 |
10 | - [NextJs](https://nextjs.org) - Next.js is an open-source web development framework.
11 | - [Typescript](https://www.typescriptlang.org) - TypeScript is a free and open-source high-level programming language.
12 | - [TailwindCSS](https://tailwindcss.com) - Tailwind CSS is a utility-first CSS framework for rapidly building modern websites without ever leaving your HTML.
13 | - [Docker](https://www.docker.com/) - Docker is a platform designed to help developers build, share, and run container applications. it handle the tedious setup, so devloper can focus on the code
14 |
15 | ## 🚀 Quick start
16 |
17 | Contributions are welcome! If you have any ideas, suggestions, or bug fixes, please open an [issue](https://github.com/Saurav-Pant/Blood-Donation-Project/issues/new/choose) or submit a pull request. Make sure to follow the project's code of conduct.
18 |
19 | > **Note**: If you are new to open source contributions, you can refer to [this](https://opensource.guide/how-to-contribute/) guide by GitHub.
20 |
21 | > **Warning**: Please do not spam the repository with unnecessary PRs. Make sure to follow the project's [Code of Conduct](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/CODE_OF_CONDUCT.md).
22 |
23 | - Go through the [CONTRIBUTING.md](https://github.com/Saurav-Pant/Blood-Donation-Project/blob/main/contributing.md) file, where all the guidelines have been mentioned that will guide you to make your contribution.
24 | - Do check out the [project issue tracker](https://github.com/Saurav-Pant/Blood-Donation-Project/issues) section.
25 |
26 | **Please give it a star to support this open source project.**
27 |
28 |
29 | ## 🤝 Our Contributors
30 |
31 |
32 | Contributors
33 |
38 |
39 |
40 | Thank you for your interest in contributing to our project! We appreciate any contributions, whether it's bug fixes, new features, or documentation improvements.
41 |
42 | We value the time and effort you put into contributing, and we look forward to reviewing and merging your contributions. Join us on this exciting journey of creativity and collaboration, and let your projects shine on Projectshut!
43 |
44 |