Hi - my org does not use Github, so unfortunately cloud isn’t a solution.
There’s also been a number of issues we’ve experienced with ECS (when it comes to deploying private repos), and was looking for a different server-less solution outside of EC2.
Amplify appears to be built around deploying js applications, but I feel like it would be possible to rig it into not knowing we’re running python/streamlit under the hood - because it really just needs to be point to the build artifacts.
I specify -t .
when I install streamlit to control where the package files are located, so hopefully simplify locating them as the AWS instance can always have weird directories.
Are these provided locally when streamlit is run? This is my current Amplify build-settings:
version: 1
frontend:
phases:
preBuild:
commands:
-yum update && yum upgrade -y
-pip3.9 install --upgrade pip
-pip3.9 install --no-cache-dir poetry
-pip3.9 install --no-cache-dir streamlit -t .
-poetry install --no-root
build:
commands:
-echo -n -e {{db_pw}} > key.bin
-echo -n -e {{db}} > encrypted.bin
-streamlit run build.py --browser.serverAddress 0.0.0.0 --server.port 80
artifacts:
baseDirectory: /app
files:
- '**/*'
cache:
paths: []