Yes! Our default stance -- barring security or other concerns -- is to make these bug reports public after we moderate. We didn't think about needing the submitter to opt-in to public status because I assumed that would be expected. @Dmitry Maslennikov I hear you that an important audience for this is the open source developer who isn't a formally licensed InterSystems customer. 

Remember we are not trying to replace the official way of handling customer bug reports, which is still via the WRC. We are simply expanding our ability to listen to users, with a way for developers who aren't operating under formal licenses -- mainly during hackathons or contests -- to get us information about problems they may be seeing.

Agreed. I think I now understand you don't need to know how to authenticate a user. Do you want to (after initial authentication) pass those authentication credentials to another app?

Also referred to as instance authentication in the documentation. 

The AI bot isn't paying attention to the Python part of the question?

Let me comment separately on the venv question. Remember, you could choose to run your flask app in a separate container and use Docker compose to orchestrate the containers. That will give you all the normal venv options.

If, however, you choose to run your flask app embedded in IRIS (running using embedded Python), you are running in-process with IRIS, and that process can't load and unload Python virtual environments while maintaining the benefits of running in embedded mode, so therefore the implication for containerization is that yes you do have to create a new base image when you want to add a package, but that's the tradeoff.

Have you seen https://github.com/grongierisc/iris-flask-template? This agrees with a lot of what you found out, but might be a little simpler. The only thing I changed for my work is my pip3 install command in Dockerfile adds a --target as recommended by @Dmitry Maslennikov:

RUN pip3 install -r requirements.txt --target /usr/irissys/mgr/python

Thank you!

For Chrome, if you know how to modify HTTP headers directly, this one seems reliable and popular (but I haven't tried it): https://chromewebstore.google.com/detail/requestly-intercept-modif/mdnl…

So now the problem isn't installing the Python library, but connecting to IRIS, correct? If you're using the above code on both servers, is the connection info the same on both servers?