Documentation for --install option, refs #223

pull/232/head
Simon Willison 2018-04-18 08:05:06 -07:00
rodzic 404fa2252b
commit 7581320823
Nie znaleziono w bazie danych klucza dla tego podpisu
ID klucza GPG: 17E2DEA2588B7F52
2 zmienionych plików z 12 dodań i 0 usunięć

Wyświetl plik

@ -173,6 +173,7 @@ This will create a docker image containing both the datasette application and th
--plugins-dir DIRECTORY Path to directory containing custom plugins
--static STATIC MOUNT mountpoint:path-to-directory for serving static
files
--install TEXT Additional packages (e.g. plugins) to install
--title TEXT Title for metadata
--license TEXT License label for metadata
--license_url TEXT License URL for metadata
@ -199,6 +200,7 @@ If you have docker installed you can use `datasette package` to create a new Doc
--plugins-dir DIRECTORY Path to directory containing custom plugins
--static STATIC MOUNT mountpoint:path-to-directory for serving static
files
--install TEXT Additional packages (e.g. plugins) to install
--title TEXT Title for metadata
--license TEXT License label for metadata
--license_url TEXT License URL for metadata

Wyświetl plik

@ -19,6 +19,16 @@ You can also define one-off per-project plugins by saving them as
``plugin_name.py`` functions in a ``plugins/`` folder and then passing that
folder to ``datasette serve``.
The ``datasette publish`` and ``datasette package`` commands both take an
optional ``--install`` argument. You can use this one or more times to tell
Datasette to ``pip install`` specific plugins as part of the process. You can
use the name of a package on PyPI or any of the other valid arguments to ``pip
install`` such as a URL to a ``.zip`` file::
datasette publish now mydb.db \
--install=datasette-plugin-demos \
--install=https://url-to-my-package.zip
Writing plugins
---------------