What the difference Wordpress setup use Server Pilot, LAMP and One Click

Posted October 1, 2016 4.6k views
WordPressUbuntu 16.04

what is the difference install wordpress using server pilot, LAMP and one click install in droplet?

One Click install Wordpress when using Droplet must wear Ram 1GB.

what the difference?

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.

Submit an Answer
2 answers

The stack used by ServerPilot is a bit more advanced than the stack used on the DigitalOcean’s one-click WordPress install.

ServerPilot uses Nginx as a reverse proxy in front of Apache and uses PHP-FPM to execute PHP scripts. There’s more info about this stack here:

I believe the stack used by DigitalOcean’s one-click installer uses a public-facing Apache server with PHP running through the older mod_php rather than the newer PHP-FPM.

Aside from the stack configuration, the main difference is that when you use ServerPilot you can manage the server after it is created through ServerPilot’s control panel without needing to SSH into your server. Things you can do through ServerPilot include creating new apps on the same server, creating additional system users, deploying Let’s Encrypt SSL certificates, and changing passwords. With servers created by DigitalOcean’s one-click installers, after the server is created you have to do all server administration by hand while SSH’d into the server.

So after creating server and connecting to serverpilot, i can also overwrite system manually from command line?
for example, the coach plan has simple http2 deployment but if i choose the free plan i can enable http2 configuring manually?

and by the way, could you please explain whats the benefit of using Apache+Nginx rather then Nginx alone?

  • You can make any customizations you need, but keep in mind ServerPilot support won’t be able to provide any support for customized servers. So, you should only do that if you’re an experienced sysadmin.

    From the ServerPilot article, here’s the reason for Apache+Nginx:

    ServerPilot configures Nginx as the public-facing web server because it is much more scalable than Apache. Unlike Apache, Nginx can handle handle tens of thousands of simultaneous client connections. As Nginx waits until it has completely received the request before proxying the request through to Apache, your server is safe from Slowloris attacks. For your SSL-enabled apps, Nginx also provides extremely efficient SSL handling and HTTP/2 support.

    • thanks for confirming.

      And yes i understand the importance of Nginx as web server. my question was whats the particular benefit of keeping Apache here.

      • You’d want Apache for .htaccess file support. Many apps like WordPress and many WordPress plugins expect to be able to control the web server through a .htaccess file. Without Apache, you’d need to do a lot of manual customization of Nginx. It’s not impossible, it just depends on where you should be spending your time and how much you can risk breakage if you’re not an expert with Nginx and server management.