.. _requirements: Requirements ======================= Provider Side ---------------- In order to install the TEKSI Wastewater module, you will need to install : * A PostgreSQL instance with PostGIS extension (check the `roadmap `_ for supported versions) .. note:: TEKSI Wastewater uses a PostgreSQL with postgis Extension database, you need to install these on your server : Recommended is to use the `EnterpriseDB `_ to make sure your postgreSQL version matches your postgis version and is installed at the right place. * Python 3.12+ (installed via OSGEO4W or using `python.org `_) * QGIS installed with the latest LTR version Recommanded is to install it with the OSGEO4W installer directly with all python packages listed. * A working pg_service file and a connexion secured to your database server (hosted or local) * TEKSI Module Management Tool (`TMMT `_) plugin installed from the QGIS plugin repository The following Python packages (installed via OSGEO4W or using `pip `_) are required: * `Psycopg `_ as database adapter * `Pydantic `_ for data validation * `Pirogue `_ for model generation and upgrades .. note:: PUM python package is automatically installed with the TMMT plugin. Client Side ---------------- For each client (workstation), you will need : * QGIS installed with the latest LTR version Recommanded is to intall it with the OSGEO4W installer directly with all python packages listed. * A working pg_service file and a connexion secured to your database server (hosted or local) * TEKSI Wastewater `plugin `_ (.zip file) * TEKSI Wastewater `project `_ (.qgs file) The following Python packages (installed via OSGEO4W or using `pip `_) are required: * `Psycopg `_ as database adapter * `sqlalchemy `_ for INTERLIS imports and exports * `geoalchemy2 `_ for INTERLIS imports and exports PostgreSQL Server side : -------------------------------------- Allow the connexion of your clients through the `postgresql.conf` file and make sure your client is allowed to reach the server postgresql port (default is 5432). TEKSI Wastewater requires PostGIS functions that did not function properly in a set of releases: * Versions before PostGIS 3.2 are not affected * When using PostGIS 3.2, the bug is fixed in Version 3.2.7 * When using PostGIS 3.3, the bug is fixed in Version 3.3.6 * When using PostGIS 3.4, the bug is fixed in Version 3.4.2 * Versions of PostGIS 3.5 or later are not affected