-
Notifications
You must be signed in to change notification settings - Fork 232
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
How to limit the number of instances that get created in DigitalOcean #128
Comments
Hello @shairyar , I cannot reproduce on DO. It is working fine for me. Can you provide me a full logtrace ? Thanks, |
This is what I see in my terminal, if there is anything you need me to provide please let me know. I got it to work with amazon which was a relief. Just so that you know i tried disabling the firewall and also with firewall enabled and I added the port I followed the steps mentioned in documentation very carefully and i went through the process multiple times just to make sure I did not miss anything
|
I'm experiencing the same problem with DO... Scrapoxy seems to keep adding more and more droplets (way more than my limit) and it also is unable to stop them in the end, I had to stop all of them manually. |
corrected in 4.0.0 |
Hey there! 🌟 Exciting news! Scrapoxy 4 is ready to rock 🚀. Check it out at Scrapoxy.io (explore the "get started" guide, deployment documentation, and more 📚). |
Hi,
I am looking for a way to limit the number of droplets that get created in DigitalOcean so while looking at the documentaion I came across this link however that does not seem to work, right now I am seeing 10 droplets and i want to reduce that to 2 if possible, I am just playing around with this library
My understanding is by adding the max I should have been able to limit the droplets but I see no difference, is this the right please to add? What am i missing here?
I even tried changing the size to
"size": "s-1vcpu-1gb"
but that did not effect anything, still it is creating more instances thatmax
specifiedThe text was updated successfully, but these errors were encountered: