rohityellapu / halodoc-patients-crud

Crud operations on patient

halodoc-patients-crud

Crud operations on patient

This repo contains the source code for Event Managing demo app rohits-event-management.com.

Table of Content

• Features
• Technologies used
• Getting started
• Installation
• Contrubuting
• Working Tree
• TroubleShooting
• Connect

Features

• Join Fabulous events connecting science and technology encouraging modern children and students to build future.
• Note down the unique ticket number after successfull registration, as the token is required for joining the event later.
• One User can register at multiple events by no user can register multiple times for a single event.
• Admin can monitor the number of registrations for event and can even monitor how many registrants are attended the event.

Technologies used

➡️JavaScript

➡️React

➡️NPM

➡️RESTful API

➡️HTTP/HTTPS

➡️HTML

➡️CSS

➡️TailWind CSS

➡️NodeJS

➡️Express

➡️RESTful API

➡️MongoDB

➡️Visual Studio Code

➡️GIT

➡️GitHub

Getting started

Prerequisites

1. Git
2. Node: any 12.x version starting with v12.0.0 or greater
3. A fork of the repo (for any contributions)
4. React

Installation

1. git clone https://github.com/rohityellapu/event-management.git to clone the repo in your local environment
2. cd event-management to go into the project root
3. npm install or npm i to install the website's npm dependencies

Running locally

1. Change apiUrl to your backend api or refer the backend implemtation task-manager-api
2. npm start to start the hot-reloading development server
3. open http://localhost:3000 to open the site in your favorite browser

Contributing

Create a branch

1. git checkout main from any folder in your local event-management repository
2. git pull origin main to ensure you have the latest main code
3. git checkout -b the-name-of-my-branch (replacing the-name-of-my-branch with a suitable name) to create a branch

Make the change

1. Follow the "Running locally" instructions
2. Save the files and check in the browser
3. Changes to React components in src will hot-reload
4. Changes to markdown files in content will hot-reload
5. If working with plugins, you may need to remove the .cache directory and restart the server

Test the change

1. If possible, test any visual changes in all latest versions of common browsers, on both desktop and mobile.
2. Run yarn check-all from the project root. (This will run Prettier, ESLint, and Flow.)

Push it

1. git add -A && git commit -m "My message" (replacing My message with a commit message, such as Fix header logo on Android) to stage and commit your changes
2. git push my-fork-name the-name-of-my-branch
3. Go to the task-manager repo and you should see recently pushed branches.
4. Follow GitHub's instructions.
5. If possible, include screenshots of visual changes. A preview build is triggered after your changes are pushed to GitHub.

Working Tree

│   .gitignore
│   package-lock.json
│   package.json
│   README.md
│   
├───public
│       index.html
│       
└───src
    │   index.js
    │   
    ├───components
    │       AddEvent.jsx
    │       Admin.jsx
    │       App.jsx
    │       Event.jsx
    │       EventDetail.jsx   
    │       Events.jsx        
    │       Loading.jsx       
    │       Login.jsx
    │       Nav.jsx
    │
    └───images
            loading.gif 

Troubleshooting

• yarn reset to clear the local cache
• If any issue faced while running the app, please let us know here

Author: Rohit Yellapu

Reach me

• Git
• Linkedin
• Twitter