Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[meta] Objectives #12

Closed
25 tasks done
Lutonite opened this issue Jan 22, 2024 · 0 comments
Closed
25 tasks done

[meta] Objectives #12

Lutonite opened this issue Jan 22, 2024 · 0 comments

Comments

@Lutonite
Copy link
Member

Lutonite commented Jan 22, 2024

Criterion Points

  • The README is well structured and explains what the web application is for with its documented application protocol interface (API)
  • The README explains the group composition and roles for each member
  • The README explains how to install and configure the server with each step
  • The README explains how to deploy, run and access the web application
  • The README explains how to configure the DNS zone to access your web application
  • The README explains how to build and publish the web application with Docker
  • The README explains how to interact with the web application with examples and outputs using curl
  • The repository is cloned using Git (HTTPS) on the server to run the web application
  • Docker and Docker Compose are correctly installed on the server
  • The Docker applications (Traefik + API) are split into multiple directories
  • The web application runs with Docker and Docker Compose on the server
  • You can access the server without a password using a SSH key
  • The web application makes usage of at least the following HTTP verbs: GET, POST, PATCH/PUT and DELETE
  • The web application can be used using a web browser, a command line tool such as curl or a custom application client
  • At least Traefik and your web application are deployed on the server
  • The applications are accessible using a domain name and/or subdomain names
  • The applications use automatic HTTPS/TLS certificate generations with Let's Encrypt
  • The domain names are correctly configured in the DNS zone
  • The presentation is clear and well prepared
  • Everyone speaks during the presentation, and the presentation lasts the time allowed
  • The presentation presents the access to the server and how to clone and run the web application
  • The presentation presents the configuration of the DNS zone with its (sub)domain names
  • The presentation presents the web application
  • A demo of the web application is made using the deployed version of the application (with curl and/or the browser)
  • The answers to the questions are correct
@Lutonite Lutonite pinned this issue Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant