README.rst 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169
  1. Installation
  2. ============
  3. Installing the system dependencies
  4. ----------------------------------
  5. To install Sydent's dependencies on a Debian-based system, run::
  6. sudo apt-get install build-essential python3-dev libffi-dev \
  7. sqlite3 libssl-dev python-virtualenv libxslt1-dev
  8. Creating the virtualenv
  9. -----------------------
  10. To create the virtual environment in which Sydent will run::
  11. virtualenv -p python3 ~/.sydent
  12. source ~/.sydent/bin/activate
  13. pip install --upgrade pip
  14. pip install --upgrade setuptools
  15. Installing the latest Sydent release from PyPI
  16. ----------------------------------------------
  17. Sydent and its dependencies can be installed using ``pip`` by running::
  18. pip install matrix-sydent
  19. Installing from source
  20. ----------------------
  21. Alternatively, Sydent can be installed using ``pip`` from a local git checkout::
  22. git clone https://github.com/matrix-org/sydent.git
  23. cd sydent
  24. pip install -e .
  25. Running Sydent
  26. ==============
  27. With the virtualenv activated, you can run Sydent using::
  28. python -m sydent.sydent
  29. This will create a configuration file in ``sydent.conf`` with some defaults. If a setting is
  30. defined in both the ``[DEFAULT]`` section and another section in the configuration file,
  31. then the value in the other section is used.
  32. You'll most likely want to change the server name (``server.name``) and specify an email server
  33. (look for the settings starting with ``email.``).
  34. By default, Sydent will listen on ``0.0.0.0:8090``. This can be changed by changing the values for
  35. the configuration settings ``clientapi.http.bind_address`` and ``clientapi.http.port``.
  36. Sydent uses SQLite as its database backend. By default, it will create the database as ``sydent.db``
  37. in its working directory. The name can be overridden by modifying the ``db.file`` configuration option.
  38. Sydent is known to be working with SQLite version 3.16.2 and later.
  39. SMS originators
  40. ---------------
  41. Defaults for SMS originators will not be added to the generated config file, these should
  42. be added to the ``[sms]`` section of that config file in the form::
  43. originators.<country code> = <long|short|alpha>:<originator>
  44. Where country code is the numeric country code, or ``default`` to specify the originator
  45. used for countries not listed. For example, to use a selection of long codes for the
  46. US/Canada, a short code for the UK and an alphanumertic originator for everywhere else::
  47. originators.1 = long:12125552368,long:12125552369
  48. originators.44 = short:12345
  49. originators.default = alpha:Matrix
  50. Docker
  51. ======
  52. A Dockerfile is provided for sydent. To use it, run ``docker build -t sydent .`` in a sydent checkout.
  53. To run it, use ``docker run --env=SYDENT_SERVER_NAME=my-sydent-server -p 8090:8090 sydent``.
  54. Persistent data
  55. ---------------
  56. By default, all data is stored in ``/data``. To persist this to disk, bind `/data` to a
  57. Docker volume.
  58. .. code-block:: shell
  59. docker volume create sydent-data
  60. docker run ... --mount type=volume,source=sydent-data,destination=/data sydent
  61. But you can also bind a local directory to the container.
  62. However, you then have to pay attention to the file permissions.
  63. .. code-block:: shell
  64. mkdir /path/to/sydent-data
  65. chown 993:993 /path/to/sydent-data
  66. docker run ... --mount type=bind,source=/path/to/sydent-data,destination=/data sydent
  67. Environment variables
  68. ---------------------
  69. .. warning:: These variables are only taken into account at first start and are written to the configuration file.
  70. +--------------------+-----------------+-----------------------+
  71. | Variable Name | Sydent default | Dockerfile default |
  72. +====================+=================+=======================+
  73. | SYDENT_SERVER_NAME | *empty* | *empty* |
  74. +--------------------+-----------------+-----------------------+
  75. | SYDENT_CONF | ``sydent.conf`` | ``/data/sydent.conf`` |
  76. +--------------------+-----------------+-----------------------+
  77. | SYDENT_PID_FILE | ``sydent.pid`` | ``/data/sydent.pid`` |
  78. +--------------------+-----------------+-----------------------+
  79. | SYDENT_DB_PATH | ``sydent.db`` | ``/data/sydent.db`` |
  80. +--------------------+-----------------+-----------------------+
  81. Internal bind and unbind API
  82. ============================
  83. It is possible to enable an internal API which allows for binding and unbinding
  84. between identifiers and matrix IDs without any validation.
  85. This is open to abuse, so is disabled by
  86. default, and when it is enabled, is available only on a separate socket which
  87. is bound to ``localhost`` by default.
  88. To enable it, configure the port in the config file. For example::
  89. [http]
  90. internalapi.http.port = 8091
  91. To change the address to which that API is bound, set the ``internalapi.http.bind_address`` configuration
  92. setting in the ``[http]`` section, for example::
  93. [http]
  94. internalapi.http.port = 8091
  95. internalapi.http.bind_address = 192.168.0.18
  96. As already mentioned above, this is open to abuse, so make sure this address is not publicly accessible.
  97. To use bind::
  98. curl -XPOST 'http://localhost:8091/_matrix/identity/internal/bind' -H "Content-Type: application/json" -d '{"address": "matthew@arasphere.net", "medium": "email", "mxid": "@matthew:matrix.org"}'
  99. The response has the same format as
  100. `/_matrix/identity/api/v1/3pid/bind <https://matrix.org/docs/spec/identity_service/r0.3.0#deprecated-post-matrix-identity-api-v1-3pid-bind>`_.
  101. To use unbind::
  102. curl -XPOST 'http://localhost:8091/_matrix/identity/internal/unbind' -H "Content-Type: application/json" -d '{"address": "matthew@arasphere.net", "medium": "email", "mxid": "@matthew:matrix.org"}'
  103. The response has the same format as
  104. `/_matrix/identity/api/v1/3pid/unbind <https://matrix.org/docs/spec/identity_service/r0.3.0#deprecated-post-matrix-identity-api-v1-3pid-unbind>`_.
  105. Replication
  106. ===========
  107. It is possible to configure a mesh of Sydent instances which replicate identity bindings
  108. between each other. See `<docs/replication.md>`_.
  109. Discussion
  110. ==========
  111. Matrix room: `#sydent:matrix.org <https://matrix.to/#/#sydent:matrix.org>`_.