hareeshr / wp-serverstack Goto Github PK

This simple script installs a LEMP stack on your server.

The server stack:

• Fast CGI Cache at the front caching all dynamic pages
• Nginx server used as its just awesome
• PHP 7.2
• MariaDB for database
• Ubuntu 16.04 running the show

• Install git

sudo apt-get install git-core

• Open Network Ports - 21(SFTP), 22(SSH), 80(HTTP), 443(HTTPS), 5062(For Admin Panel), 40000:42000(Passive Connection for FTP)

This Setup is tested with Google CDN and Amazon CloudFront CDN.

sudo git clone https://github.com/hareeshr/wp-serverstack
sudo chmod 755 wp-serverstack/install.sh
sudo ./wp-serverstack/install.sh

Note: To install manually(Interactive mode):

• clone this repository
• open -manual.sh file and copy-paste blocks of code with relevant changes in ssh client

The script uses several parameters to setup your server for example: the website name, FTP username, Database Name

Installation Example

./install.sh -w=example.com ip=127.0.0.1 -ftpu=MYFTP -ftpp=MYPASS

• NGINX
• PHP 7.2
• MariaDb
• VsFTPd
• phpMyAdmin
• Adminer
• Basic File Manager
• Net2FTP
• Simple Control Panel

Control panel can be accessed by https://ip:5062 or https:tools.example.com:5062

Control Panel is secured by Basic HTTP Authentication. The user credentials are set using the parameters Admin Username and Password(or use default username password which is obviously not secure).

Use ssl-dns-route53.sh to install certbot and issue SSL certificates automatically by DNS challenge with AWS Route53 Integration. This requires a IAM user with valid Access Key and Secret having access to AmazonRoute53FullAccess Policy

Usage Example

./ssl-dns-route53.sh -w=example.com -rak=access_key -ras=access_secret

Parameters

For other DNS services use ssl-dns.sh with same parameters as above (excluding AWS credentials). In this method, you'll be asked to manually add TXT record for your domains and subdomains for verification.

You may also use ssl-dns-route53-manual.sh and ssl-dns-manual.sh files to copy paste to SSH console manually to have more control.

Certbot Renewal

Only route53 method is eligible to renew as the other method is a manual process. You can test run renewal by running

certbot renew --dry-run

If the test run is success, you can now actually renew the certificates

certbot -q renew --renew-hook 'service nginx reload'

You may also add this to your crontab to run the renewal script periodically

#open crontab
crontab -e
#select 2 to select nano
#add the following to the bottom and save - CTLR+X
30 2 * * 1 certbot -q renew --renew-hook 'service nginx reload'

#run SSL renewal script
certbot -q renew --renew-hook 'service nginx reload'

#cronjob
crontab -e
30 2 * * 1 certbot -q renew --renew-hook 'service nginx reload'

#nginx service commands
sudo systemctl status nginx.service
sudo systemctl stop nginx.service
sudo systemctl start nginx.service
sudo systemctl restart nginx.service
sudo systemctl enable nginx.service

#PHP service commands
sudo systemctl status php7.2-fpm
sudo systemctl stop php7.2-fpm
sudo systemctl start php7.2-fpm
sudo systemctl restart php7.2-fpm
sudo systemctl enable php7.2-fpm

#MySQL service commands
sudo systemctl status mysql.service
sudo systemctl stop mysql.service
sudo systemctl start mysql.service
sudo systemctl restart mysql.service
sudo systemctl enable mysql.service

#VsFTPd service commands
sudo systemctl status vsftpd.service
sudo systemctl stop vsftpd.service
sudo systemctl start vsftpd.service
sudo systemctl restart vsftpd.service
sudo systemctl enable vsftpd.service