github/datasette
1
0
Fork 0
mirror of https://github.com/simonw/datasette.git synced 2025-12-10 16:51:24 +01:00
Code Issues Projects Releases Packages Wiki Activity

Fix --metadata doc usage (#1112)

Browse source 
Thanks, @jefftriplett.
This commit is contained in:
Jeff Triplett 2020-11-28 13:53:48 -06:00 • committed by GitHub
commit bbde835a1f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/changelog.rst
View file

@ -453,7 +453,7 @@ You can now create :ref:`custom pages <custom_pages>` within your Datasette inst
:ref:`settings_dir` (`#731 <https://github.com/simonw/datasette/issues/731>`__) allows you to define a custom Datasette instance as a directory. So instead of running the following::
$ datasette one.db two.db \
--metadata.json \
--metadata=metadata.json \
--template-dir=templates/ \
--plugins-dir=plugins \
--static css:css
@ -770,7 +770,7 @@ Small changes
0.28 (2019-05-19)
-----------------
A `salmagundi <https://adamj.eu/tech/2019/01/18/a-salmagundi-of-django-alpha-announcements/>`__ of new features!
A `salmagundi <https://adamj.eu/tech/2019/01/18/a-salmagundi-of-django-alpha-announcements/>`__ of new features!
.. _v0_28_databases_that_change:

2
docs/settings.rst
View file

@ -23,7 +23,7 @@ Configuration directory mode
Normally you configure Datasette using command-line options. For a Datasette instance with custom templates, custom plugins, a static directory and several databases this can get quite verbose::
$ datasette one.db two.db \
--metadata.json \
--metadata=metadata.json \
--template-dir=templates/ \
--plugins-dir=plugins \
--static css:css