Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
rbrands authored Jul 30, 2020
1 parent f1597d2 commit bdcd101
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,19 +5,19 @@
Everything you need to organize and track a "MeetUp", e.g. organizing a group bike-ride.

The first idea for this application came up during "Corona"-time: In order to arrange group bike rides or other "MeetUps"
with ensuring the traceability of the participants, the corresponding tool was missing.
ensuring the traceability of the participants the corresponding tool was missing.

Therefore the following design principles for this web-app are:
* Easy to use without complicated registration and authentication process. Therefore only "keywords" are used as very basic access control.
* Responsive design, usable on PC and smartphones
* Easy to use without complex registration and authentication process. Therefore only "keywords" are used as very basic access control.
* Responsive design, usable on PC and smartphones with all modern brwosers (Chrome, Edge, Firefox, Safari) supporting the <a href="https://webassembly.org/">WebAssembly Standard</a>.
* Minimal administrative effort: All meetups data should be deleted automatically after the configured time (typically 28 days). Everyone should be able to organize a MeetUp.
* Availability of "private" MeetUps: The ability to organize a MeetUp and protect it with a "keyword" that can be given to potential participants.
* Adaptable: The application has a front-end layer implemented with <a href="https://docs.microsoft.com/en-us/aspnet/core/blazor">ASP.NET Core Blazor</a> The application logic is provided as microservices (<a href="https://docs.microsoft.com/en-us/azure/azure-functions/">Azure Functions</a>). In this way it is possible to use the application layer independently with a different front-end.

# About this repository
* Folder "MeetUpFunctions" has the source code of the Azure Functions used for the backend. The master branch is CI enabled with GitHub Actions and deployed to the slot "dev" of the Azure Functions App.
* Folder MeetUpPlanner holds the source code of the Blazor WebAssembly and the ASP.NET Core hosting app. The master branch is CI enabled with GitHub Action and deployed to https://meetup-planner-dev.azurewebsites.net
* Client - The Blazor Web Assembly project
* Client - The Blazor WebAssembly project
* Server - The ASP.NET Core web backend for the application
* Shared - Model classes shared with all projects for serializing the objects to JSON

Expand Down

0 comments on commit bdcd101

Please sign in to comment.