Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
More flexible CORS support in core, to encourage good security practices
See original GitHub issueIt would be nice if the --cors option accepted an origin regex to more securely allow secure local development.
As an example, Observable notebooks namespace every user’s notebooks by their username and user content is served from username.observableusercontent.com, so you would set --cors-origin username.observableusercontent.com to restrict access to a local development Datasette instance to only your own notebooks, rather than exposing the data to any website that makes a request.
Thank you for all of your work on Datasette!
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think the right way to do this is to support multiple optional
--cors-origin=pattern values, like you suggested.This may involve a breaking change to the CLI settings interface, so I’m adding this to the 1.0 milestone.