1) The link you reference is invalid: https://docs.bitnami.com/installer/infrastructure/mean/administration/create-custom-ap…
2) When we started the initial thread, I was very grateful for you help and explanations. Then, I wanted to go onto the next issue. So, I posted a reply to the same thread. But, you had already marked it as completed. After waiting a bit, with no response, I thought perhaps no one would address the next issue because the topic was different. So, I started another thread. Then, I found discrepancies in the documentation and felt really frustrated. The apache server stuff is completely new to me and I have a pressing project for which I already have the applications working. I just needed to be able to access them securely.
3) My first approach was to try the httpd-prefix.conf method, which I could not get to work. So, I though perhaps the code needed to be in a special folder "/opt/bitbnami/apps ...", but the documentation also indicated a projects folder, so I was confused. Hence, I started a thread to question the difference in documentation. No one replied. So I continued trying different approaches. That led me to the next thread.
So, I opened mutiple threads because I tried different approaches and ran into different sets of problems. The third thread I posted, no one responded until I posted I had solved it on my own.
In the future, I will post one thread. And it my needs change, I will just keep on listing the questions within the same thread. But, if someone marks it as completed, and I want to ask more questions, will anyone look at it ?
I believe the topics were different. One was a plea for where to put code. Another was my encounter with differences in the documentation. And, the third was a very detailed description of what worked and what did not work when trying to serve multiple node apps. Nowhere in the documentation is there an explanation that it does not matter where you put the code for an app. What does matter is that you have to tell apache server where the code can be found, for example: Document Root and Directory directives in the vhost files. My guess is that the httpd-prefix.conf approach might also work if it is possible to describe the directives in that file as well.
So, I apologize for posting multiple threads. I assumed that is what was necessary.