A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Scalable compute services.
Worry-free setup & maintenance.
Simple object storage.
Run managed Kubernetes clusters.
Easily distribute traffic.
Attach scalable volumes.
Deploy pre-built applications.
Connect, share and learn
DevOps and development guides
Questions & Answers
Development and systems Q&A
by Justin Ellingwood
Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below.
I just ran into an issue today where my Droplet limit got set to zero and was not reset when I updated my billing information which I have a ticket on.
However, this droplet limit concerns me a great deal.
It seems very counter productive for a system designed for use by developers.
Lets say I am developing a VOIP application. I figure each server can handle say 100 users. Then when I hit 100 users I deploy a new droplet from a master record.
This means if I have a large number of sign ups I could hit my droplet limit and my application would just break. Then I would not be able to process new orders until I open a support ticket and make a request.
Which since you do not even notify people when they hit the droplet limit I would have to check on my own.
It seems it would just be easier at this point just to use Rackspace or Amazon for any real production useage and just use Digital Ocean to play with since your limiting developers so much with this horrible idea.