You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+22-27Lines changed: 22 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,50 +6,45 @@ With a minimal amount of config for each app, it handles deployment, plus ingres
6
6
It will also install a "Streamlit Hub" app in your cluster, that allows you to view all running apps as well as launch
7
7
new apps from the UI.
8
8
9
-
## Installation
10
-
11
-
Details to come
12
-
13
9
## Prerequisites
14
10
15
11
This app has been developed under the assumption that you're running a cluster on EKS in AWS. It will likely work on other clusters
16
12
with minimal changes, but this has not been tested.
17
13
18
-
## Usage
19
-
20
-
The operator is built around one StreamlitApp CRD that takes required configuration for each app.
14
+
## Installation
21
15
22
-
Currently users must specify four pieces of config:
16
+
The Streamlit Operator comes prepackaged as a Helm chart. If you've never used helm, please refer to
17
+
Helm's [documentation](https://helm.sh/docs) to get started.
23
18
24
-
-`name`: The name of the app. This will be used as the name of the deployment, service, ingress, and DNS record.
25
-
-`repo`: The git style URL of the repo containing the app code. This is used to clone the repo into the container. e.g. `[email protected]:MyOrg/my-app.git`
26
-
-`branch`: The branch of the repo to use. Typical usecase will be to track main, but users can also work off development branches.
27
-
-`code_dir`: The directory within the repo that contains the app code. This is used to run `streamlit run` within the container. e.g. `my-app`
28
-
- Note that the operator assumes your app's entrypoint is `main.py` within this directory. This will be configurable in the future.
19
+
Once Helm has been set up correctly, add the repo as follows:
If you had already added this repo earlier, run `helm repo update` to retrieve
46
-
the latest versions of the packages. You can then run `helm search repo
47
-
<alias>` to see the charts.
38
+
The operator is built around one StreamlitApp CRD that takes required configuration for each app.
48
39
49
-
To install the <chart-name> chart:
40
+
Currently users must specify four pieces of config:
50
41
51
-
helm install my-<chart-name> <alias>/<chart-name>
42
+
-`name`: The name of the app. This will be used as the name of the deployment, service, ingress, and DNS record.
43
+
-`repo`: The git style URL of the repo containing the app code. This is used to clone the repo into the container. e.g. `[email protected]:MyOrg/my-app.git`
44
+
-`branch`: The branch of the repo to use. Typical usecase will be to track main, but users can also work off development branches.
45
+
-`code_dir`: The directory within the repo that contains the app code. This is used to run `streamlit run` within the container. e.g. `my-app`
46
+
- Note that the operator assumes your app's entrypoint is `main.py` within this directory. This will be configurable in the future.
0 commit comments