Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate validator #31

Open
eFrane opened this issue Apr 19, 2017 · 2 comments
Open

Integrate validator #31

eFrane opened this issue Apr 19, 2017 · 2 comments
Assignees
Milestone

Comments

@eFrane
Copy link
Member

eFrane commented Apr 19, 2017

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:

  1. A user enters an endpoint url to be validated and an email
    address at which they want to be notified once validation
    completes.
  2. The information is enqueued and eventually processed by
    a validation job
  3. The results of the validation are stored for further processing
    and formatted into a neat email for the customer.
@eFrane eFrane self-assigned this Apr 27, 2017
eFrane added a commit that referenced this issue Nov 24, 2017
eFrane added a commit that referenced this issue Nov 24, 2017
eFrane added a commit that referenced this issue Nov 24, 2017
eFrane added a commit that referenced this issue Nov 24, 2017
@eFrane
Copy link
Member Author

eFrane commented 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
Copy link
Member Author

eFrane commented 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.

@eFrane eFrane added this to the v1.0 milestone Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant