How to install BigTree CMS with Nginx on CentOS 6.9

To install BigTree CMS with Nginx on CentOS 6.9

In our previous post we have seen about the installation of BigTree CMS on CentOS 6.9. For watching the mentioned tutorial, click on the https://www.linuxhelp.com/how-to-install-bigtree-cms-on-centos-6-9/ Now we are going to see about the installation procedure of BigTree CMS with Nginx on CentOS 6.9. BigTree CMS is an open source content management system (CMS) built on PHP and MySQL. It is very extensible applications with user friendly interface and it is very easy to use. BigTree CMS is a fast, light-weight and open source content management system built based on PHP and MySQL. It was created mainly by content strategy experts mainly for a better user experience. BigTree CMS comes with lots of modules that can be used to manage complex content like blog posts, formatted news releases, calendar events, frequently asked questions, and homepage features.

Pre - Requisite

Before proceeding the installation process, check whether the target system has been installed with LEMP environment. Using MySQL create a database and an user for Backdrop CMS, also provide privileges for the created user.

Installation procedure

Enter the prompt into the Nginx HTML directory by running the cd command as follows.

[root@linuxhelp1 ~]# cd /usr/share/nginx/html/

Next go to BigTree CMS official site and download the CMS package to the target system by running the wget command followed by the download link.

[root@linuxhelp1 html]# wget https://www.bigtreecms.org/ajax/download-installer/?installer=60& email=
[1] 28772
[root@linuxhelp1 html]# --2017-09-22 12:04:02--  https://www.bigtreecms.org/ajax/download-installer/?installer=60
Resolving www.bigtreecms.org... 69.20.113.170
Connecting to www.bigtreecms.org|69.20.113.170|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5798266 (5.5M) [application/zip]
Saving to: “ index.html?installer=60” 

100%[======================================> ] 5,798,266    328K/s   in 35s     

2017-09-22 12:04:40 (161 KB/s) - “ index.html?installer=60”  saved [5798266/5798266]

Extract the downloaded file using unzip command.

[root@linuxhelp1 html]# unzip index.html?installer=60
Archive:  index.html?installer=60
   creating: BigTree-CMS/
  inflating: BigTree-CMS/.gitmodules  
  inflating: BigTree-CMS/README.md   
  inflating: BigTree-CMS/bigtree.sql  
   creating: BigTree-CMS/core/
   creating: BigTree-CMS/core/admin/
.
.
inflating: BigTree-CMS/install.php  
  inflating: BigTree-CMS/license.txt  

Next open and edit the PHP configuration file using vim editor and add a time zone in the file. Save and exit the file.

[root@linuxhelp1 html]# vim /etc/php.ini
date.timezone = Asia/Kolkata

Edit the php-fpm configuration file using vim editor and make the following changes in the file. Save and exit the file.

[root@linuxhelp1 html]# vim /etc/php-fpm.d/www.conf

listen = /var/run/php-fpm/php-fpm.sock
listen.owner = nginx
listen.group = nginx
user = nginx
group = nginx

Edit the Nginx configuration file using vim editor and enter the following changes. Save and exit the file.

[root@linuxhelp1 html]# vim /etc/nginx/conf.d/default.conf

server {
    listen       80 default_server 
    listen       [::]:80 default_server 
    server_name  _ 
    root         /usr/share/nginx/html 
    # Load configuration files for the default server block.
    include /etc/nginx/default.d/*.conf 
    index index.html index.php 
    location ~ \.php {
    fastcgi_index index.php 
    fastcgi_split_path_info ^(.+\.php)(.*)$ 
    include /etc/nginx/fastcgi_params 
    fastcgi_pass unix:/var/run/php-fpm/php-fpm.sock 
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name 
    }
   error_page 404 /404.html 
        location = /40x.html {
    }
    error_page 500 502 503 504 /50x.html 
        location = /50x.html {
    }
}

Change the ownership of php-fpm file by executing the following command.

[root@linuxhelp1 html]# chown nginx:nginx /var/run/php-fpm/php-fpm.sock

Change the ownership of the file in Nginx directory.

[root@linuxhelp1 html]# chown -R nginx:nginx /usr/share/nginx

Restart the Nginx service.

[root@linuxhelp1 html]# service nginx restart
Stopping nginx:                                            [  OK  ]
Starting nginx:                                            [  OK  ]

Switch over to the browser and enter the URL as https://machineip/Bigtree-cms. The installation wizard of BigTree CMS will appear on the screen.

Enter the required database details.

Enter the required admin details.

After entering the required details and select the Install Now option to proceed with the installation process. Click install now option.

The installation is now complete. To open the admin area, click the given link to the admin area along with the configured credentials.

Enter the required admin credentials and click login.

The admin dashboard of BigTree CMS appears on the screen.

Thus concludes the installation procedure of BigTree CMS with Nginx on CentOS 6.9.

FAQ
Q
Can I use BigTree with a nginx web server?
A
Yes, BigTree will work on an ngninx environment but does not come with out of the box support. You'll need to add directives to either your global nginx configuration file or your virtual host as laid out here.
Q
How does BigTree CMS stack up against the competition?
A
We think it's the best, but don't take our word for it. BigTree CMS was recently ranked in the Top 50 CMS platforms available within the industry.
Q
How many other people are using BigTree CMS?
A
While we don't require a registration of BigTree for downloading it, we can share that over 7,000 people have dowloaded the most recent version of BigTree, and the forum has over 700 active users.
Q
I'm seeing a page with broken styles or a 500 error after installing BigTree, what's up?
A
Many shared hosts have issues with .htaccess files. We have a section dedicated to some common platforms for installing BigTree.
Q
How do I suggest a new BigTree feature?
A
Users and developers are welcome to submit feature requests through the Feature Requests channel in our Forum.