Feature/UI Deployment and Request Structure

[EnricoBausenhart]

Type of Change

• 🐛 Bug fix
• ✨ New feature
• ♻️ Code refactor
• 📝 Documentation update
• 🚀 Performance improvement
• ✅ Test addition/update
• 🧹 Chore/maintenance
• 📐 API Spec update
• Other (please describe):

Changes

• AWS deployment:

  • nip.io reached a limit of requested certificates for the provided url -> sslip.io is now used to host the deployment
  • use existing elastic ip "meetatmensa-ip" in the AWS Lab to tackle the problem with dynamic URL's (was a blocker for Auth0 allowed callbacks and CORS problems)
  • use a better ec2 instance due to performance issues with t2.micro
  • add database images to compose.aws.yml to complete setup
  • add AWS Url to allowed origins of the Gateway

• Client Dockerfile

  • as we have different setups we need different API_BASE_URL's within our vite application -> normally vite bakes these env variables into the application at build time
  • use of a small shell script entrypoint.sh to inject the variable dynamically
  • environment variable added in compose.yml for local deployment
  • environment variable renamed in compose.aws.yml
  • environment variable added in values.yaml (helm) of the client
  • Result: one Dockerfile can be used for all deployments

• UI Refactoring

  • remove unused subpaths like /preferences
  • add userID to create match request
  • added team logo to the drawer
  • display Skeletons while requests are loading for better user experience
  • mock data can now be enabled with a VITE env variable for testing
  • improved handling of initial login and handling of userID within the application
  • refactoring of request code architecture -> separate service for each of the types (user / matchrequests / matches)
  • several small bug fixes

• Networking fixes

  • Moved deployment back to Chair's Rancher after temporarily moving it to an instance on a personal server during the outage.
  • Configured ingress, TLS, and DNS on the Chair's Rancher.

[EnricoBausenhart]

@stark-cybertech Do we have go back to the "latest" tag in charts/client/values.yaml? The feature tag was only for testing, right?

[stark-cybertech]

@stark-cybertech Do we have go back to the "latest" tag in charts/client/values.yaml? The feature tag was only for testing, right?

Yes! Please go back to latest!

[stark-cybertech]

This looks excellent, but will not deploy successfully to the chair's Rancher instance yet because of the changes made to networking.

I'm working on shifting the DNS records and setting up a reverse proxy on Chair rancher, lets wait for that before merging this.

[stark-cybertech]

Just tested the CI/CD action and deployment to rancher is working smoothly!

Still struggling with the following issue though:

Where:

GET @ api/v2/user/me

When:

On start when first fetching user-id

Error:

Browser reports "CORS request did not succeed"

Cause:

Special character "|" in URL, part of the auth0 ID.

Solution:

Encode "|" as "%7C"

[stark-cybertech]

Deployment works and no major issues with the client! Ready to deploy! 🤘🤘