Lawyer-Consultation-System

This repository contains CSE471 Lab Group No 11 PROJECT, Spring 2023 Section 05.

Group Information

• Athar Noor Mohammad Rafee [20101396]
• Faria Islam Laiba [20301176]
• Shornali Islam Snikdha [20301108]

System Requirements

To test and run the application, or if you want to modify things according to your needs

you will have to install the following things.

1. java

   jdk version 17 or higher. Download jdk if you don't have it already.

   If you're on unix like system, you can use SDK MAN which has certain advantages over other methods.

   To check your version of java, run:

    java --version

2. node

   node version 16.15.1 or higher. Download node if you don't have it already.

   To check your version of node, run:

    node --version

3. npm

   npm version 5.6.1 or higher. You will have it after you install node.

   To check your version of npm, run:

    npm --version

4. A valid vaadin pro subscription or student subscription

   For more information, visit vaadin

Setup

to set up, please follow these steps:

1. Clone the repo

   make sure that you have git installed. To check run git --version in your terminal.

    git clone https://github.com/Inmoresentum/Lawyer-Consultation-System.git

2. Change directory to the project directory

   cd Lawyer-Consultation-System

   or open this directory with your favourite code editor or IDE which will download all the dependencies for maven. We used IntelliJ IDEA but other code editors or IDES will also do the job.

3. Click the play icon which will start the spring boot application and will recursively download all the npm dependencies. Alternatively, from the terminal use maven to build and run using ./mvnw clean install.

4. By default, the server should start http://localhost:8080

Issues

you've found a bug in the source code, a mistake in the documentation? you can help by submitting an issue on GitHub. before you create an issue, make sure to search for the issue archive -- your issue may have already been addressed!

please try to create bug reports that are:

• reproducible. include steps to reproduce the problem.
• specific. include as much detail as possible: which version, what environment, etc.
• unique. do not duplicate existing opened issues.
• scoped to a single bug. one bug per report.