Skip to content

Releases: peermaute/MealSquare

MealSquare API v3.0

07 Nov 07:17

Choose a tag to compare

MealSquare API v3.0

The third release revolves around creating a stable, production ready release that is also up and running on GCP.

Features

  • Authorization added
    → Firebase authentication was added. The provided interface AuthenticationHandler also makes it easy to use a different Authorization Service. Any authenticated user can create new Meals, but only the creator or admin users can update or delete a Meal.
  • API published
    → The API can now be accessed via https://api.mealsquare.peermaute.com. Feel free to fill the database with some new recipes!
  • Meals contain images now
    → The Meal.class has a new field "image" so an image file can be stored for any Meal.
  • API Documentation
    → The API is now documented using the OpenAPI standard. A .yaml file can be found here. The new welcome page of the website also contains a link to an HTML version.

What else is there to note?

  • CI/CD-Pipeline is now fully set up. The release contains a Dockerfile that makes it easy to implement.
  • MealSquare got its own logo. Check the README.md or the website to check it out!

MealSquare v2.0

30 Jul 12:27

Choose a tag to compare

MealSquare v2.0

The second release expands the features of the first release and fixed some issues.

Features

  • Meal must not contain ingredient
    → Feature to filter that meals do not contain given ingredient
  • Create Meal Plan
    → You can now create a meal plan.
    This meal plan can be customized by using the filter feature and specifying the number of days (default 5).
  • Read CSV file
    → Reading CSV files is now possible. Other file formats can be easily added with using the interface (not planned for now).

What else is there to note?

  • Fixed pipeline issue (MongoDB tests could only be run locally)
  • The next release will focus on bringing the backend live

MealSquare v1.0

16 May 13:23

Choose a tag to compare

MealSquare v1.0

This first release includes the backend and revolves around single meals.
Meal plans and frontend will be added in a future release.

Features

  • CRUD operations
  • Filter meals by:
    • name
    • carb base (for example "noodles")
    • contains a certain ingredient (for example "carrots")
    • tags (for example "mediterranean")
    • maximum preparation time
  • REST API

What else is there to note?

  • The MongoDB is currently connected to a cloud database. This is configured with a connection string in the application.properties file.
  • The functionalities are tested with JUnit tests.