EasyEngine is one of the simplest ways to install WordPress fully functional on a LEMP stack; including rewrite and SSL certificates. Please note that if you use a shared kernel environment like OpenVZ it is very likely you will not be able to run Docker and EasyEngine. A quick overview of what we plan to accomplish today:
- Stop and Remove Apache/Postfix/Sendmail
- Install EasyEngine LEMP Stack
- Install WordPress
- Enable EE Admin
By default Apache is installed on most Distro’s so we are going to stop it and remove it from the system. Additionally, if you have installed Postfix or Sendmail we are going to stop and remove them as well.
sudo service postfix stop
sudo service sendmail stop
sudo apt remove apache2* postfix* sendmail*
sudo apt purge apache2* postfix* sendmail*
We need to grab EasyEngine then install. You will notice we use && often, if you are new to Linux it is a way to combine multiple commands.
wget -qO ee https://rt.cx/ee4 && sudo bash ee
Install WordPress using EE with SSL
We are going to install WordPress and specify a few extra commands to specify our own email, username, password and install SSL using LetsEncrypt.
sudo ee site create yourdomain.com --type=wp --ssl=le --firstname.lastname@example.org --admin-user=yourusername --admin-pass=yourpassword
Once installation is complete it will output all the relevant site information including MySQL database login information. Should you ever need to pull it up later for reference you can run sudo ee site info yourdomain.com
At this point you should be able to point your browser to yourdomain.com and see that a newly installed WordPress site is waiting for you.
Enable EE Admin
Now lets enable EE Admin. This will give you access to PhpMyAdmin, Nginx status, opcache-gui and a few others.
Next you can check the authorized users list.
# Below is a sample output you should see.
| username | password |
| easyengine | blahpass |
Connect to EE Admin by https://yourdomain.com/ee-admin/.
As of this post, EE has a bug where it will not start automatically at boot. It is currently being worked on, however, running sudo ee service restart nginx-proxy will ensure it starts. You can add a script in /etc/init.d/ should you want it to run this command on boot, until the bug is fixed.
Any questions or comments please comment below.