4 ms·

That publish command looks sweet! For confidential data I'd have to setup some integration with our infra to get the required access control though. Maybe rathe

That publish command looks sweet! For confidential data I'd have to setup some integration with our infra to get the required access control though. Maybe rather go with the package option using docker and a pipeline that deploys to our k8s where I could handle auth using an existing proxy... My current workflow doesn't really involve creating databases, I mostly just create foreign tables, normal tables and views in a default DB. From time to time I then just dump-backup everything away and start fresh. Thanks for the response and your tools in general though, I liked how everything just worked when I tried it :-)

simonw 4y ago
For confidential data you could use one of the plugins that add authentication - datasette-auth0 or datasette-auth-github or datasette-auth-passwords are options there - but yeah, you're probably better off deploying to internet hosting if you already have an auth proxy setup somewhere.
- sally_glance 4y ago
  Oh wow thx for the pointer, I overlooked those. For business I would need a more generic oauth- or saml-based one to work with our Keycloak, but for quick private/hobby sharing the password one looks perfect.
- simonw 4y ago
  Meant to say internal hosting, not internet hosting.