-
Notifications
You must be signed in to change notification settings - Fork 69
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
Documentation for self-hosting? #365
Comments
Hello, The Dockerfile is not published into the registry because it's not doing nothing special, just exposing a Node.js server that will be used for receiving the traffic. If publisth the Docker image will help you to adopt the project I can publish it, I did that before for exampel at https://github.com/Kikobeats/docker-vips, just tell me 🙂 |
Not sure if I understand. Is If so, then yes it would be very helpful to have the Docker image in a registry, so that users can self-host without having to fork and maintain. |
It's stateless, although it work better if you provide a Redis URI for caching purpose: why not use the public endpoint rather than run your own instance? just curiosity 🙂 |
We want to self-host due to the rate limiting. The actual rate limit doesn't seem to be consistent in headers, but from what I gather it's 50 reqs per 24 hours, per IP. That is way too low for our use case. Thanks for confirming the hosting details! It would be great to have an image in the registry, especially with an |
Hi there, just coming across this project. Although Avatar API seems fantastic, their pricing simply does not scale if your use case is bulk data processing.
unavatar seems more limited, but it's fantastic to see an OSS implementation.
That said, I was unable to find any documentation on self-hosting. I have looked through the Dockerfile, and might suggest that you publish builds to Dockerhub or another registry.
The text was updated successfully, but these errors were encountered: