-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
eFrane
added a commit
that referenced
this issue
Nov 23, 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
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 25, 2017
This is technically done but currently in reconsideration since the actual server load for running the validator goes way over the expected load. |
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
address at which they want to be notified once validation
completes.
a validation job
and formatted into a neat email for the customer.
The text was updated successfully, but these errors were encountered: