Why does the one-click wordpress install needs 30GB disk space


DO has a one-click install for wordpress which is only available for the 1GBram/30GBssd plan.

I am curious why this is the case since if i would install LAMP on ubuntu myself it will work with the 20GBssd space easily.


  1. Does DO one-click install for wordpress uses more space than if i do a manual install with ubuntu on LAMP for worpress?
  2. How much disk-space is available after the one-click install of wordpress on a 30GBssd?
  3. Is there another advantage if i do it manually than the opportunity to run it on a 500mb/20GBssd? Is the one-click install unproper?
  4. Do i still need to configure sendmail and curl (PHP) after the one-click install?
  5. Is there a reason why a CENTOS one-click install is not provided yet?
  6. I am using atm 12GB disk space for 8 tld-domains with 250mb ram on a shared host since 4 years. Do you really advise me to start with the 1GB plan?

Thanks for your time … and wisdom numbering your answer like above.



Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hi Stevan,

We’ve restricted the WordPress one-click to the 1GB/30GB droplet not because of any storage limitation, but instead for memory reasons. WordPress running on Apache/MySQL tends to use a lot of memory, and 512mb isn’t always enough. In order to ensure a smoother experience for users using the one-click, we’ve restricted it to only be usable on the 1GB droplet, or larger.

The WordPress one-click isn’t all that different from deploying WordPress yourself: we just did most of the work for you. It doesn’t use any additional space (about 1.8GB is used by the OS, supporting libraries, and WordPress itself), has sendmail pre-configured, and is pretty much ready to use out of the box. php5-curl isn’t included, but it’s not a direct dependency for WordPress either.

When you deploy your own WordPress install, you can optimize it specifically for your needs, use a stack other than LAMP, and deploy it on the smaller, 512mb droplet. It’s just a bit more work on your part.

All of our One-Clicks are based on Ubuntu LTS releases, since most users are familiar with Ubuntu. We haven’t seen much demand for other distros used as the base for one-clicks, and when we had other distros as bases, they mostly went unused. You may want to check out our GitHub repository for User-Data Scripts, however. It contains additional scripts you can use at Droplet creation to deploy different applications and stacks to a Droplet using the distribution of your choice. Here’s the WordPress script for CentOS 7, for instance.

Finally, if you feel more comfortable using a 512mb droplet, you can absolutely do so. We recommend the 1GB one since we’ve seen better performance with at least 1GB of memory, but it’s really up to you. However, keep in mind that you cannot really compare a VPS to a Shared host. A VPS (like our Droplets) has a lot more overhead, since you’re running an entire server.

I hope that helped clear things up! Let me know if I missed anything. :)

Best, Eris Platform Support Specialist

@eris “Wordpress 4.7 on 16.04” is now available for the first plan, why does this differ? Thanks in advance!

Hi Erin

Thanks for your serious response!

You say that it is because of RAM and it obiously is but on the “create droplet” page if you select the 5$ plan and hover over the one-click install from wordpress it states “please select a disk size of at least 30gb” which is kind of mishinting to the real reason.

The second question left is why don’t leave the RAM issue with wordpress to the user, for most microblogs it would be sufficent.

thanks for the link to the centos!

Can we somehow compare a shared host’s RAM to a VPS’s RAM considering the overhead you mentioned?

Thanks for your time and knowledge :) Regards