Week 02

Main considerations:

We will be using gitflow branching model: https://nvie.com/posts/a-successful-git-branching-model/. It is recommended to use git rebase instead of git merge into your own branch.

We will use ASP.NET Core MVC as "ASP.NET Core is a cross-platform, high-performance, open-source framework for building modern, cloud-enabled, Internet-connected apps". Part of the .NET ecosystem, primarily using C#, a statically typed language known for its robustness and versatility. C# is also strongly typed making our program safe.
We are using Model-View-Controller (MVC) pattern. The Model represents the data and business logic, the View is the user interface, and the Controller handles the input, converting it to commands for the Model or View.
Razor pages is a page-based programming model that makes building web UI easier and more productive.
NET 8.0 is the latest long-term supported release

Database service using Dabber(ORM) and sqLite (it was a requirement, since we took the same as the python programming language used). Dabber is chosen because {}
Dependency injection is implemented so we can easily change the database service.

We have provided a Dockerfile in the repository root, which enables us to automate the process of building the project's image and running it in an independent container.
This Dockerfile relies on two official .NET images: the Software Development Kit (SDK) image, which provides all the tools for building, compiling, testing, and debugging .NET applications; and the .NET ASP Runtime Environment, which provides the environment to run our .NET ASP application.
This Dockerfile also contains all database specific files. This approach will most likely be changed at a future point in time, where the database will be configured to run on an independent container.

We added a .NET project template to streamline the setup or development process.
Tests were added to ensure code reliability and detect bugs early in the development process. Unfortunatelly the tests don't fully work yet, as both code and tests have to have slight adjustments.
We implemented a feature for user registration, allowing new users to create accounts.
The original HTML pages have been converted to Razor pages. Some adjustments have been made, but overall, we are keeping the 1:1 copy of the Mini-Twit
We use a session cookie to store a unique identifier for the user's session on the server. This mechanism is a part of the session state feature, which allows ASP.NET Core applications to maintain user-specific data across multiple HTTP requests. Session cookies help maintain user-specific state information between different requests made during the same session. This is particularly useful in persisting user data across multiple pages.
All endpoints are implemented into asp.net core application.
Chatgpt was used to translate small parts of code/methods. not everything if fully correct. And we still heavily used the Microsoft Documentation along with Chatgpt.
TODO: talk about who worked on what.

we need to consider how our url actions work. There are multiple ways of doing it in ASP.NET Core and we are mixing it
we know that the current way of authentication is not entirely secure, but we will look at security later.