Deployment makes an application available to its intended users by hosting it where they can reach it. For a Streamlit app, that means keeping the server running and replacing localhost with an accessible URL. section 5.1.1
Choose an approach according to the audience, budget, and operational effort:
- Share a server over a local network for household, testing, or limited workplace use. It works only while the host computer remains on and connected. section 5.1.2
- Use Streamlit Community Cloud for free, beginner-friendly public sharing, with code stored in a remote GitHub repository. section 5.2 section 5.5
- Use a dedicated server or cloud provider when the app needs more control, memory, traffic capacity, or a professional domain. section 5.1.2 section 12.1
You can now view your Streamlit app in your browser. Local URL: http://localhost:8501 Network URL: http://192.168.50.68:8501
Compare the local URL used on the host computer with the network URL that lets another device on the same network open the app. section 5.1.2
A practical public deployment connects GitHub to Community Cloud, specifies dependencies in requirements.txt, and moves confidential values into production secrets. Keep local credentials in .streamlit/secrets.toml, exclude that file with .gitignore, and store production values in App Settings. section 5.5
Production needs can change over time. Docker packages the app for portability, while AWS deployment can provide more control; custom domains and HTTPS make the hosted application feel more professional. section 12.0
Deploying a to-do list app
Push the local app to GitHub, point Streamlit Community Cloud to the repository, and share its resulting web address so anyone with internet access can use it. section 5.2
