Summary of Q&A session contents from 20.05.2021 with relevance for the NUM-App backend

[alena456]

📖 This discussion summarizes the backend related contents about which we talked in the last NUM-App Enabling session on the 20th of May 2021. Check-out the discussion in the general or frontend repository for additional hints!

[alena456]

Q: Can the backend only be deployed on OpenShift?
A: The NUM-App documentation assumes that the app is deployed on an OpenShift cluster in order to take advantage of the following aspects:

1. OpenShift guarantees no vendor lock-in
2. OpenShift is open source
3. OpenShift provides integrated developer workflows such as S2I
4. Logging and metric services can be used out of the box
5. The web console provides unified access to the OpenShift capabilities
   Because of the containerization it is very easy to scale the application according to different loads. Moreover, data separation is simplified when deploying the app for multiple projects or use cases.
   However, the mobile backend can of course also be deployed outside of a Kubernetes or an OpenShift cluster. You will then need to set up a PostgrSQL database by yourself but can still leverage the existing scripts to setup the required tables.

[alena456]

Q: What should you keep in mind when developing on Windows?
A: Run bash scripts that are defined in the documentation in the Git Bash or Commander to not run into problems with special Linux commands like cat or base64.

If you notice a gap in the documentation regarding the set-up of the solution on Windows please let us know and create a documentation issue!