Please report any errors you encounter at https://github.com/Intevation/intelmq-webinput-csv/issues
For upgrade instructions, see UPGRADING.md.
- An installed python3 hug
- An installed intelmq (<=v2.3.3) installation on the same machine.
- Optional sqlite3 for authentication
- An installed yarn
Currently the only way to install Webinput-CSV is to clone the repository and do a manual installation. The following steps will guide through the installtion from source.
-
Clone the repository
git clone https://github.com/Intevation/intelmq-webinput-csv.git
-
Install using pip3
cd intelmq-webinput-csv pip3 install .
-
Build the client
cd client yarn && yarn build
-
Configuration files
Webinput-CSV is searching for config files in the following order:
- A file specified via enviroment varibale (WEBINPUT_CSV_CONFIG=/my/folder/webinput_csv.conf)
- The IntelMQ config folder (e.g. /opt/intelmq/etc)
- The system wide config folder (/etc/intelmq/)
-
(Optional) Authentication
To integrate and activate the authentication for Webinput-CSV create a config file similar to the example. Webinput-CSV is searching for session configs in the following order:
- A file specified via enviroment varibale (WEBINPUT_CSV_SESSION_CONFIG=/my/folder/webinput-session.conf)
- The IntelMQ config folder (e.g. /opt/intelmq/etc)
- The system wide config folder (/etc/intelmq/)
The configured path to the sqlite3 database has to be read and writeable by the user running the backend. If the file does not exist it will be created on startup.
To insert users into the database, there is a script called
webinput-adduser
. -
Create Apache2 configuration
Make sure the Apache2 (or intelmq or the configured) user has read access to the folders containing the front- and backend. A configuration snippet for Apache can be found in
config/apache-example/003_intelmq_webinput_csv.conf
. Adapt the WSGIScriptAlias URL and path to your needs. On Debian systems the required wsgi package is calledlibapache2-mod-wsgi-py3
. For the backend the apache has to listen on port 8667. The path prefix for the backend must be used in the apache config!
The application is now available via browser on the machine and the configured path prefix, e.g. http://localhost/webinput