-
Notifications
You must be signed in to change notification settings - Fork 10
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
📝 [maykinmedia/django-setup-configuration#1] document setup_configura…
…tion command and env vars
- Loading branch information
1 parent
656d894
commit f3c34da
Showing
3 changed files
with
144 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,135 @@ | ||
.. _installation_config_cli: | ||
|
||
|
||
=================== | ||
Configuration (CLI) | ||
=================== | ||
|
||
After deploying Objecttypes API and Objects API, they need to be configured to be fully functional. The | ||
command line tool ``setup_configuration`` assist with this configuration: | ||
|
||
* It uses environment variables for all configuration choices, therefore you can integrate this with your | ||
infrastructure tooling such as init containers and/or Kubernetes Jobs. | ||
* The command can self-test the configuration to detect problems early on | ||
|
||
You can get the full command documentation with: | ||
|
||
.. code-block:: bash | ||
src/manage.py setup_configuration --help | ||
.. warning:: This command is declarative - if configuration is manually changed after | ||
running the command and you then run the exact same command again, the manual | ||
changes will be reverted. | ||
|
||
Preparation | ||
=========== | ||
|
||
The command executes the list of pluggable configuration steps, and each step | ||
required specific environment variables, that should be prepared. | ||
Here is the description of all available configuration steps and the environment variables, | ||
use by each step for both APIs. | ||
|
||
|
||
Objects API | ||
=========== | ||
|
||
Sites configuration | ||
------------------- | ||
|
||
Configure the domain where Objects API is hosted | ||
|
||
* ``SITES_CONFIG_ENABLE``: enable Site configuration. Defaults to ``True``. | ||
* ``OBJECTS_DOMAIN``: a ``[host]:[port]`` or ``[host]`` value. Required. | ||
* ``OBJECTS_ORGANIZATION``: name of Objects API organization. Required. | ||
|
||
Objecttypes configuration | ||
------------------------- | ||
|
||
Objects API uses Objecttypes API to validate data against JSON schemas, therefore | ||
it should be able to request Objecttypes API. | ||
|
||
* ``OBJECTS_OBJECTTYPES_CONFIG_ENABLE``: enable Objecttypes configuration. Defaults | ||
to ``True``. | ||
* ``OBJECTTYPES_API_ROOT``: full URL to the Objecttypes API root, for example | ||
``https://objecttypes.gemeente.local/api/v1/``. Required. | ||
* ``OBJECTTYPES_API_OAS``: full URL to the Objecttypes OpenAPI specification. | ||
* ``OBJECTS_OBJECTTYPES_TOKEN``: authorization token. Required. | ||
* ``OBJECTS_OBJECTTYPES_PERSON``: Objects API contact person. Required. | ||
* ``OBJECTS_OBJECTTYPES_EMAIL``: Objects API contact email. Required. | ||
|
||
Demo user configuration | ||
----------------------- | ||
|
||
Demo user can be created to check if Objects API work. It has superuser permissions, | ||
so its creation is not recommended on production environment. | ||
|
||
* ``DEMO_CONFIG_ENABLE``: enable demo user configuration. Defaults to the value of the ``DEBUG`` setting. | ||
* ``DEMO_PERSON``: demo user contact person. Required. | ||
* ``DEMO_EMAIL``: demo user email. Required. | ||
* ``DEMO_TOKEN``: demo token. Required. | ||
|
||
|
||
Objecttypes API | ||
=============== | ||
|
||
ObjectTypes API has similar configuration steps as the Objects API. | ||
|
||
Sites configuration | ||
------------------- | ||
|
||
Configure the domain where Objects API is hosted | ||
|
||
* ``SITES_CONFIG_ENABLE``: enable Site configuration. Defaults to ``True``. | ||
* ``OBJECTTYPES_DOMAIN``: a ``[host]:[port]`` or ``[host]`` value. Required. | ||
* ``OBJECTTYPES_ORGANIZATION``: name of Objecttypes API organization. Required. | ||
|
||
Objects configuration | ||
--------------------- | ||
|
||
Objects API uses Objecttypes API to validate data against JSON schemas, therefore | ||
it should be able to request Objecttypes API. | ||
|
||
* ``OBJECTS_OBJECTTYPES_CONFIG_ENABLE``: enable Objecttypes configuration. Defaults | ||
to ``True``. | ||
* ``OBJECTTYPES_API_ROOT``: full URL to the Objecttypes API root, for example | ||
``https://objecttypes.gemeente.local/api/v1/``. Required. | ||
* ``OBJECTTYPES_API_OAS``: full URL to the Objecttypes OpenAPI specification. | ||
* ``OBJECTS_OBJECTTYPES_TOKEN``: authorization token. Required. | ||
|
||
Demo user configuration | ||
----------------------- | ||
|
||
The similar configuration as in Objects API. | ||
|
||
* ``DEMO_CONFIG_ENABLE``: enable demo user configuration. Defaults to the value of the ``DEBUG`` setting. | ||
* ``DEMO_PERSON``: demo user contact person. Required. | ||
* ``DEMO_EMAIL``: demo user email. Required. | ||
* ``DEMO_TOKEN``: demo token. Required. | ||
|
||
|
||
Execution | ||
========= | ||
|
||
|
||
With the full command invocation, everything is configured at once and immediately | ||
tested. | ||
|
||
.. code-block:: bash | ||
src/manage.py setup_configuration | ||
You can skip the self-tests by using the ``--no-selftest`` flag. | ||
|
||
.. code-block:: bash | ||
src/manage.py setup_configuration --no-self-test | ||
``setup_configuration`` command checks if the configuration already exists before changing it. | ||
If you want to change some of the values of the existing configuration you can use ``--overwrite`` flag. | ||
|
||
.. code-block:: bash | ||
src/manage.py setup_configuration --overwrite |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,5 +16,6 @@ this. | |
|
||
quickstart | ||
config | ||
config_cli | ||
deployment/index | ||
oidc |