Skip to content

Commit

Permalink
[#2977] Improve wording of best practice regarding name clashes.
Browse files Browse the repository at this point in the history
The documentation previously talked about sharing databases which could
be misunderstood as the possibility of sharing PostgreSQL databases
between CKAN instances (instead of sharing Redis databases, which was
the intended meaning).
  • Loading branch information
torfsen committed Sep 12, 2016
1 parent 74aabf9 commit 4ef202b
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions doc/extensions/best-practices.rst
Expand Up @@ -80,10 +80,10 @@ the name of your extension. For example:
begin with the name of your extension. For example
``my_extension:super-special-job-queue``.

In some situations, resources like databases may even be shared between
multiple CKAN *instances*, which requires an even higher degree of uniqueness
for the corresponding names. In that case, you should also prefix your
identifiers with the CKAN site ID, which is available via
In some situations, a resource may even be shared between multiple CKAN
*instances*, which requires an even higher degree of uniqueness for the
corresponding names. In that case, you should also prefix your identifiers with
the CKAN site ID, which is available via

::

Expand Down

0 comments on commit 4ef202b

Please sign in to comment.