An open source multi-tool for exploring and publishing data
 
 
 
 
 
 
Go to file
Simon Willison 03933b3084 .prettierrc, refs #1166 2020-12-31 13:25:44 -08:00
.github/workflows Switch to google-github-actions/setup-gcloud - refs #1126 2020-12-03 19:12:33 -08:00
datasette Refactor out sqlite_extensions option 2020-12-29 14:16:05 -08:00
docs sqlite-utils now lives at sqlite-utils.datasette.io 2020-12-29 13:38:53 -08:00
tests Modernize code to Python 3.6+ (#1158) 2020-12-23 09:04:32 -08:00
.coveragerc Configure code coverage, refs #841, #843 2020-06-13 13:48:23 -07:00
.dockerignore Run CI on GitHub Actions, not Travis 2020-08-17 22:09:34 -07:00
.gitattributes New explicit versioning mechanism 2020-10-28 20:38:15 -07:00
.gitignore New run_sanity_checks mechanism, for SpatiLite 2019-05-11 15:55:30 -07:00
.isort.cfg Used isort to re-order my imports 2018-05-14 00:04:23 -03:00
.prettierrc .prettierrc, refs #1166 2020-12-31 13:25:44 -08:00
Dockerfile Fixed URLs to SpatiaLite files, refs #931 2020-08-12 13:49:50 -07:00
LICENSE Initial commit 2017-10-22 17:39:03 -07:00
MANIFEST.in Include LICENSE in sdist (#1043) 2020-10-23 13:54:34 -07:00
README.md News is now on datasette.io/news 2020-12-10 15:24:16 -08:00
codecov.yml codecov should not be blocking 2020-07-02 21:29:32 -07:00
pytest.ini Port Datasette from Sanic to ASGI + Uvicorn (#518) 2019-06-23 20:13:09 -07:00
setup.cfg New explicit versioning mechanism 2020-10-28 20:38:15 -07:00
setup.py Update pytest requirement from <6.2.0,>=5.2.2 to >=5.2.2,<6.3.0 (#1145) 2020-12-16 13:44:39 -08:00
update-docs-help.py Use f-strings in place of .format() 2020-11-15 15:24:22 -08:00

README.md

Datasette

PyPI Changelog Python 3.x Tests Documentation Status License docker: datasette

An open source multi-tool for exploring and publishing data

Datasette is a tool for exploring and publishing data. It helps people take data of any shape or size and publish that as an interactive, explorable website and accompanying API.

Datasette is aimed at data journalists, museum curators, archivists, local governments and anyone else who has data that they wish to share with the world.

Explore a demo, watch a video about the project or try it out by uploading and publishing your own CSV data.

Want to stay up-to-date with the project? Subscribe to the Datasette Weekly newsletter for tips, tricks and news on what's new in the Datasette ecosystem.

Installation

If you are on a Mac, Homebrew is the easiest way to install Datasette:

brew install datasette

You can also install it using pip or pipx:

pip install datasette

Datasette requires Python 3.6 or higher. We also have detailed installation instructions covering other options such as Docker.

Basic usage

datasette serve path/to/database.db

This will start a web server on port 8001 - visit http://localhost:8001/ to access the web interface.

serve is the default subcommand, you can omit it if you like.

Use Chrome on OS X? You can run datasette against your browser history like so:

 datasette ~/Library/Application\ Support/Google/Chrome/Default/History

Now visiting http://localhost:8001/History/downloads will show you a web interface to browse your downloads data:

Downloads table rendered by datasette

datasette serve options

Usage: datasette serve [OPTIONS] [FILES]...

  Serve up specified SQLite database files with a web UI

Options:
  -i, --immutable PATH      Database files to open in immutable mode
  -h, --host TEXT           Host for server. Defaults to 127.0.0.1 which means
                            only connections from the local machine will be
                            allowed. Use 0.0.0.0 to listen to all IPs and
                            allow access from other machines.
  -p, --port INTEGER        Port for server, defaults to 8001
  --reload                  Automatically reload if database or code change
                            detected - useful for development
  --cors                    Enable CORS by serving Access-Control-Allow-
                            Origin: *
  --load-extension PATH     Path to a SQLite extension to load
  --inspect-file TEXT       Path to JSON file created using "datasette
                            inspect"
  -m, --metadata FILENAME   Path to JSON file containing license/source
                            metadata
  --template-dir DIRECTORY  Path to directory containing custom templates
  --plugins-dir DIRECTORY   Path to directory containing custom plugins
  --static STATIC MOUNT     mountpoint:path-to-directory for serving static
                            files
  --memory                  Make :memory: database available
  --config CONFIG           Set config option using configname:value
                            docs.datasette.io/en/stable/config.html
  --version-note TEXT       Additional note to show on /-/versions
  --help-config             Show available config options
  --help                    Show this message and exit.

metadata.json

If you want to include licensing and source information in the generated datasette website you can do so using a JSON file that looks something like this:

{
    "title": "Five Thirty Eight",
    "license": "CC Attribution 4.0 License",
    "license_url": "http://creativecommons.org/licenses/by/4.0/",
    "source": "fivethirtyeight/data on GitHub",
    "source_url": "https://github.com/fivethirtyeight/data"
}

Save this in metadata.json and run Datasette like so:

datasette serve fivethirtyeight.db -m metadata.json

The license and source information will be displayed on the index page and in the footer. They will also be included in the JSON produced by the API.

datasette publish

If you have Heroku or Google Cloud Run configured, Datasette can deploy one or more SQLite databases to the internet with a single command:

datasette publish heroku database.db

Or:

datasette publish cloudrun database.db

This will create a docker image containing both the datasette application and the specified SQLite database files. It will then deploy that image to Heroku or Cloud Run and give you a URL to access the resulting website and API.

See Publishing data in the documentation for more details.