Crates.io | check-if-email-exists-grpc |
lib.rs | check-if-email-exists-grpc |
version | 1.0.0 |
source | src |
created_at | 2021-09-15 13:26:38.361894 |
updated_at | 2022-10-02 17:00:53.29835 |
description | A GRPC wrapper around check-if-email-exists |
homepage | https://gitlab.com/j3a-solutions/check-if-email-exists-grpc |
repository | https://gitlab.com/j3a-solutions/check-if-email-exists-grpc |
max_upload_size | |
id | 451814 |
size | 120,706 |
This crate is a wrapper around the HTTP version of check-if-email-exists. It exposes a Grpc API instead of Rest.
If you are looking for a SaaS solution for your email validation, then please check Reacher by the original creator of check-if-email-exists
.
Why would you use this version?
There is a docker image here. It supports the same environment variables than the executable.
If you're using Docker as container runtime, then you may want to use the --init
option in order to pass signals to the process.
See the helm chart in this repo
For this, you'd need to build the application using cargo build
The proto
files are published in the Buf Schema Registry. You can then use Buf to generate the code in the language of your choice. Just follow the docs
This crate exports a grpc client in the module proto::v0::service_client
There are several environment variables:
BIND_ADDRESS | Description | Default Value |
---|---|---|
REDIS_HOST | Redis IP | 127.0.0.1 |
REDIS_PORT | Redis port | 6379 |
REDIS_DB | Redis database to connect to | 0 |
REDIS_USERNAME | Redis username | "" |
REDIS_PASSWORD | Redis password | "" |
CACHE_EXP_SECONDS | How long each validation output is stored in Redis (in seconds) | 86400 |
RUST_LOG | Logging level | check_if_email_exists_grpc=info |
This project is published under the AGPL-3.0, or Affero General Public License, version 3, as per the license requirements of check-if-email-exists