Repository navigation
Integrate validator #31
Description
Integrate OParl/validator into the website. This is depends on #29,
because we can't run the validator without liboparl present.
The validation flow on the website should be as follows:
- A user enters an endpoint url to be validated and an email
address at which they want to be notified once validation
completes. - The information is enqueued and eventually processed by
a validation job - The results of the validation are stored for further processing
and formatted into a neat email for the customer.
Activity
refs #31: Configure the validation queue job
refs #31: Move progress output into callback
refs #31: Minor fixes
refs #31: Change validator stable version to `production`
refs #31: Validation failure handling
refs #31: Configure the validation queue job
refs #31: Move progress output into callback
refs #31: Minor fixes
refs #31: Change validator stable version to `production`
refs #31: Validation failure handling
refs #31: Disable process timeout for validation (workers have fallba…
eFrane commentedon Feb 7, 2018
This is technically done but currently in reconsideration since the actual server load for running the validator goes way over the expected load.
eFrane commentedon Feb 14, 2018
Status Update:
The validator will be provided as a dockerized flask application which will do the heavy lifting. This also means that this issue is no longer related to #29.
Development of the afore mentioned application can be followed at OParl/validator-api.