mirror of
https://gitlab.com/etc404/software-engineering-project.git
synced 2026-05-10 20:52:58 +00:00
Finaly did the README.md
This commit is contained in:
Madeleine Stamp
@@ -1,93 +1,146 @@
|
|||||||
# Software Engineering Project
|
# Recipe Management Application
|
||||||
|
|
||||||
|
## Overview
|
||||||
|
The Recipe Management Application is a web-based system that allows users to create, view, update, and delete recipes. Recipes and ingredients are stored in a MySQL database and displayed through a web interface.
|
||||||
|
|
||||||
|
The application is built using Spring Boot for the backend, Thymeleaf for the frontend, and MySQL for data storage. The project is managed using GitLab for version control.
|
||||||
|
|
||||||
## Getting started
|
---
|
||||||
|
|
||||||
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
|
## Technologies Used
|
||||||
|
|
||||||
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
|
Backend
|
||||||
|
- Java
|
||||||
|
- Spring Boot
|
||||||
|
- Spring Data JPA
|
||||||
|
|
||||||
## Add your files
|
Frontend
|
||||||
|
- Thymeleaf
|
||||||
|
- HTML / CSS
|
||||||
|
|
||||||
* [Create](https://docs.gitlab.com/user/project/repository/web_editor/#create-a-file) or [upload](https://docs.gitlab.com/user/project/repository/web_editor/#upload-a-file) files
|
Database
|
||||||
* [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
|
- MySQL
|
||||||
|
|
||||||
|
Tools
|
||||||
|
- Maven
|
||||||
|
- GitLab
|
||||||
|
- Eclipse or IntelliJ
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Features
|
||||||
|
|
||||||
|
- Create recipes
|
||||||
|
- View all recipes
|
||||||
|
- View recipe details
|
||||||
|
- Update recipes
|
||||||
|
- Delete recipes
|
||||||
|
- Store ingredients in a database
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Project Structure
|
||||||
|
|
||||||
```
|
```
|
||||||
cd existing_repo
|
src/main/java/com/example/demo
|
||||||
git remote add origin https://gitlab.com/etc404/software-engineering-project.git
|
│
|
||||||
git branch -M main
|
├── controller
|
||||||
git push -uf origin main
|
├── service
|
||||||
|
├── service/impl
|
||||||
|
├── entity
|
||||||
|
├── dto
|
||||||
|
├── repository
|
||||||
|
└── exception
|
||||||
|
|
||||||
|
src/main/resources
|
||||||
|
├── templates
|
||||||
|
├── static
|
||||||
|
└── application.properties
|
||||||
```
|
```
|
||||||
|
|
||||||
## Integrate with your tools
|
---
|
||||||
|
|
||||||
* [Set up project integrations](https://gitlab.com/etc404/software-engineering-project/-/settings/integrations)
|
## Setup Instructions
|
||||||
|
|
||||||
## Collaborate with your team
|
### 1. Clone the Repository
|
||||||
|
|
||||||
* [Invite team members and collaborators](https://docs.gitlab.com/user/project/members/)
|
```bash
|
||||||
* [Create a new merge request](https://docs.gitlab.com/user/project/merge_requests/creating_merge_requests/)
|
git clone https://gitlab.com/your-repository-name.git
|
||||||
* [Automatically close issues from merge requests](https://docs.gitlab.com/user/project/issues/managing_issues/#closing-issues-automatically)
|
cd your-repository-name
|
||||||
* [Enable merge request approvals](https://docs.gitlab.com/user/project/merge_requests/approvals/)
|
```
|
||||||
* [Set auto-merge](https://docs.gitlab.com/user/project/merge_requests/auto_merge/)
|
|
||||||
|
|
||||||
## Test and Deploy
|
### 2. Create the Database
|
||||||
|
|
||||||
Use the built-in continuous integration in GitLab.
|
```sql
|
||||||
|
CREATE DATABASE recipe_db;
|
||||||
|
```
|
||||||
|
|
||||||
* [Get started with GitLab CI/CD](https://docs.gitlab.com/ci/quick_start/)
|
### 3. Configure Database Connection
|
||||||
* [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/user/application_security/sast/)
|
|
||||||
* [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/topics/autodevops/requirements/)
|
|
||||||
* [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/user/clusters/agent/)
|
|
||||||
* [Set up protected environments](https://docs.gitlab.com/ci/environments/protected_environments/)
|
|
||||||
|
|
||||||
***
|
Edit `src/main/resources/application.properties`
|
||||||
|
|
||||||
# Editing this README
|
```properties
|
||||||
|
spring.datasource.url=jdbc:mysql://localhost:3306/recipe_db
|
||||||
|
spring.datasource.username=root
|
||||||
|
spring.datasource.password=yourpassword
|
||||||
|
|
||||||
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
|
spring.jpa.hibernate.ddl-auto=update
|
||||||
|
spring.jpa.show-sql=true
|
||||||
|
|
||||||
## Suggestions for a good README
|
spring.thymeleaf.cache=false
|
||||||
|
```
|
||||||
|
|
||||||
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
|
### 4. Run the Application
|
||||||
|
|
||||||
## Name
|
Using Maven:
|
||||||
Choose a self-explaining name for your project.
|
|
||||||
|
|
||||||
## Description
|
```bash
|
||||||
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
|
mvn spring-boot:run
|
||||||
|
```
|
||||||
|
|
||||||
## Badges
|
Or run the main Spring Boot application file in your IDE.
|
||||||
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
|
|
||||||
|
|
||||||
## Visuals
|
---
|
||||||
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
|
|
||||||
|
|
||||||
## Installation
|
## Access the Application
|
||||||
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
|
|
||||||
|
|
||||||
## Usage
|
Open a browser and go to:
|
||||||
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
|
|
||||||
|
|
||||||
## Support
|
```
|
||||||
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
|
http://localhost:8080
|
||||||
|
```
|
||||||
|
|
||||||
## Roadmap
|
---
|
||||||
If you have ideas for releases in the future, it is a good idea to list them in the README.
|
|
||||||
|
|
||||||
## Contributing
|
## GitLab Workflow
|
||||||
State if you are open to contributions and what your requirements are for accepting them.
|
|
||||||
|
|
||||||
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
|
Create a branch for new features:
|
||||||
|
|
||||||
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
|
```bash
|
||||||
|
git checkout -b feature/feature-name
|
||||||
|
```
|
||||||
|
|
||||||
## Authors and acknowledgment
|
Commit changes:
|
||||||
Show your appreciation to those who have contributed to the project.
|
|
||||||
|
|
||||||
## License
|
```bash
|
||||||
For open source projects, say how it is licensed.
|
git add .
|
||||||
|
git commit -m "Description of changes"
|
||||||
|
```
|
||||||
|
|
||||||
## Project status
|
Push to GitLab:
|
||||||
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
|
|
||||||
|
```bash
|
||||||
|
git push origin feature/feature-name
|
||||||
|
```
|
||||||
|
|
||||||
|
Then create a Merge Request.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Contributors
|
||||||
|
|
||||||
|
- Moon Gibson
|
||||||
|
- Cristian Gonzalez
|
||||||
|
- Kai HahnHansen
|
||||||
|
- Madeleine Stamp
|
||||||
|
- Autumn Wolf
|
||||||
|
|||||||
Reference in New Issue
Block a user