Any way to handle authentication / passwords?; perhaps via config persisted via browser? #109
Description
@LukeAFullard . Thanks for your work on this. It's been a while since I have looked as WASM. Lack of ability to protect secrets was what previously limited my usage. I'm not sure if that has been solved in any way. My use-cases involves connecting to a DuckDB hosted on an S3 bucket, requiring credentials, which one would not want to embed in the html. I was looking at your file-persistence demo and wondering if that can be used somehow by users to load a config or secrets.toml file on a home screen. These would define env variables in the browser for usage with a streamlit app. I'd be interested in your thoughts. Thanks.