Using package from a private repo in Streamlit deploy

[CloudySnake]

Has anyone looked at deploying a streamlit app that references a python package hosted in a private repository? We have a common code library that we reference in Pipfile which will pip install from a private GitHub repo we own. For non-streamlit deployments our CI/CD system is given a specific SSH key with permissions to access this repo, but we don’t (currently, as far as I see) have that option in Streamlit yet.

Figured I’d ask if anyone has tried this and might have found a solution.

[CloudySnake]

Just a reply to say - I spoke to the nice guys and gals at Streamlit and (hopefully they won’t mind me sharing this) they said this feature is on the roadmap but no confirmed delivery date for now.

For the time being we’re just bundling the private repo code in to our streamlit app repo and we’ll worry about handling updates with a good old copy & paste from time to time.

[Luiz_Scheuer]

Any updates on this? Know of any similar threads?

[Goyo]

Check this answer of mine to a similar question.

Secrets at build time

Oh, I misread. One straightforward way is not making it part of the build but instead making your startup code install it the import fails. Like people usually do in google colab notebooks.

[snehankekre]

@Luiz_Scheuer Here’s a thread on the same topic:

PIP Installing from Github

Hi @sophiegeoghan and @C-Roensholt I had no luck via the requirements.txt route either What worked was installing the package in the main app script itself via a subprocess. Say your script is streamlit_app.py. Include the following at the very top of your app: import streamlit as st import subprocess import sys import time try: # replace "yourpackage" with the package you want to import import yourpackage # This block executes only on the first run when your pac…