This repository has been archived by the owner on Nov 13, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #4
Closes #9
Deployment
I had created a Dockerfile in order to deploy the streamlit app to google cloud run. Testing it out on a personal google cloud account project, there was a problem with the websocket connection. Upon further reading of this github issue and this streamlit forum, it is safe to say Google cloud run really shouldn't be used to deploy streamlit projects. However, that does not mean it is impossible.
Workaround
In order to the healthz conflict, we encounter upon deployment, created an app.yaml file and edited the dockerfile to hack around the error. This is not pretty and really shouldn't be done, but this is the only way I found to get around this error. You can read in more detail about the solution from this comment. Ideally, we would just not deploy comet circle with streamlit or not use google cloud run.
Instructions
I have also provided instructions on how to deploy this project on any google cloud project in the README.md. Very simple and is just two commands.