bonifatius94 / aspnetefcoretest Goto Github PK

Issue:

• HTTPS does not work properly when using ASP.NET with docker
• would be nice to have a fully-working boilerplate
• final goal: make sure the curl commands in the API test script work without the -k option for the HTTPS endpoint

Suggested Solution:

• figure out what's the matter, try out following tutorials: https://docs.microsoft.com/de-de/aspnet/core/security/docker-compose-https?view=aspnetcore-5.0 and https://docs.microsoft.com/de-de/aspnet/core/security/docker-https?view=aspnetcore-5.0
• check if it's about trusting the self-signed CA of the dev cert on Linux, see https://askubuntu.com/questions/645818/how-to-install-certificates-for-command-line
• think about generating valid letsencrypt certs that are commonly trusted by any webbrowser using dockerized certbot, see https://certbot.eff.org/docs/install.html#running-with-docker

Issue:

• the current data schema is very simple (just one table)
• in real-world use cases there are lots of related entities (1-1, 1-n, m-n) with various data types
• therefore add examples for each use case to have proper samples

Suggested Solution:

• add at least one relationship for each mapping type (1-1, 1-n, m-n)
• try out various data types, default value initialization strategies, ...
• add proper controllers making use of the new schema
• add component tests (update test script)

Issue:

• the current procedure uses only self-signed certs
• for real-world applications it would be useful to know how to use e.g. Let's Encrypt certs

Suggested Solution:

• find a way to generate Let's Encrypt certs, e.g. certbot: https://hub.docker.com/r/certbot/certbot/ and https://certbot.eff.org/docs/install.html#running-with-docker
• once a certificate was successfully created, try to include it into the project (document how it was achieved in README)