Toggle navigation

LAPP Image Guide

Version 5.6

Websoft9 LAPP is a pre-configured, ready to run image for running LAPP on Alibaba Cloud.

The LAPP stack is an open source web platform that can be used to run dynamic web sites and servers. It is considered by many to be a powerful alternative to the more popular LAMP stack and includes Linux, Apache, PostgreSQL (instead of MySQL) and PHP, Python and Perl.

Application Software Directory
Software default directory: /data/wwwroot
Software configuration directory:  /etc/httpd/conf.d

Infrastructure(PHP7.0,APACHE2.4)
PHP Configuration File: /etc/php.ini
Default Apache Vhost Configuration File: /etc/httpd/conf.d/vhost.conf
Apache Vhost Configuration directory: /etc/httpd/conf.d
Apache Log Files: /var/log/httpd

Database(PostgreSQL)
Database install directory: /usr/pgsql-9.5
Database data directory: /data/postgresql
Database configuration File: /data/postgresql/*.conf
Adminer directory:/data/wwwroot/adminer/
Using Chrome or Firefox to visit: http://ip/adminer

After the installation of Image,please verify it

  • Login on Alibaba Cloud console,get you Internet IP Address
  • Open you Chrome or Firefox on your local PC,visit the http://Internet IP Address and you can enter the phpinfor page directly,if there no response from browser,please check the Security Group settings to ensure that port 80 is been allowed

Three usernames and passwords are required for application installation, application using, andapplication maintenance:

1、PostgreSQL Database:Default username and password is postgres/postgres
Control Panel URL:http://Internet IP Address/phpmyadmin
2、Linux Server:Username is root,Password is set by youself when buying.
Please Using the Putty for ssh remote and WinSCP for SFTP

Note:You can reset the password of OS through Cloud Console if you have forgotten it

 

Connect to a Linux instance using Windows OS

This section uses PuTTY as an example. PuTTY can be downloaded here.

You can connect to a Linux instance via PuTTY as follows:

  1. Start Putty.exe.
  2. Enter the public IP address of the instance in Host Name (or IP address).
  3. Use the default port 22.
  4. Select SSH as Connection Type.
  5. Type a session name in Saved Sessions, and then click Save. In later logins, you may directly load the session without re-entering the IP address.
  6. Click Open to connect.
  7. Upon first connection, the following dialog box will be displayed. Click Yes.
  8. As prompted, enter the username and password for the Linux ECS instance. The password will not be displayed on-screen. Press the Enter key to complete connection to the instance.

When you connect your computer to the Linux instance successfully, you can operate the instance from your computer.

Use SFTP you can mange file,upload and download file,configure Server.

  1. Start WinSCP. Login Dialog will appear.
  2. Then select your File protocol(SFTP) on the dialog
  3. Enter your host name to Host name field, username to User name and password to Password like below
  4. You may want to save your session details to a site so you do not need to type them in every time you want to connect. Press Save button and type site name.
  5. When appear the dialog below,please select the “yes”
  6. You can manane Linux file below
  7. WinSCP can integrate the Putty and transfer the log in information to Putty
  8. Now you can use Putty(Not need to log in) from the menu bar of WinSCP

Following is the step for access phpMyadmin

  1. Open Chrome or Firefox on your local PC
  2. visit the http://Internet IP Address/adminer,you can enter the login page
  3. select you language,Username:postgres,Password:postgres
  4. Click the button “Login”

There are five main steps to deploying a apps in a LAPP environment:

① upload source code -> ② modify the file system user permissions -> ③ configure the domain name (optional) -> ④ increase the site corresponding database (optional) -> ⑤ complete the installation wizard

LAPP environment only deployed a website or multiple sites, there is no domain name corresponding to the deployment of these two cases the details of the operation is slightly different, the following were explained:

Scenario 1: The server installs only one application

  1. Using SFTP to upload your source code to the default directory: /data/wwwroot
  2. Using Putty to modify the owner of user,just run the fllowing command:
    ~# chown -R apache.apache /data/wwwroot
  3. If have not domain,please visit the http://Internet IP Address/ to start intallation wizard
  4. If have domain,please complete the domain name resolution and then visit the http://Domain/ to start intallation wizard
  5. If you are prompted during the installation wizard database can not be created automatically, you need to create a database through: http:// Internet IP Address/adminer

Scenario 2: Server deployment multiple apps (no domain)

In the case of no domain, the deployment of two apps as an example, the specific operation is as follows:

  1. Using SFTP to upload your source code directory(e.g.named mysite1) to the default directory: /data/wwwroot
  2. Using Putty to modify the owner of user,just run the fllowing command:
    ~# chown -R apache.apache /data/wwwroot/mysite1
  3. Please visit the http://Internet IP Address/mysite1 to start intallation wizard
  4. If you are prompted during the installation wizard database can not be created automatically, you need to create a database through: http:// Internet IP Address/adminer

Install the second website(e.g.named mysite2 ), the same steps

Scenario 3: Server deployment multiple websites (share a domain)

In the case of no domain, the deployment of two apps as an example, the specific operation is as follows:

  1. Using SFTP to upload your source code directory(e.g.named mysite1) to the default directory: /data/wwwroot
  2. Using Putty to modify the owner of user,just run the fllowing command:
    ~# chown -R apache.apache /data/wwwroot/mysite1
  3. Please complete the domain name resolution(add A record to the Internet IP Address of you Server)
  4. Please visit the http://Domian/mysite1 to start intallation wizard
  5. If you are prompted during the installation wizard database can not be created automatically, you need to create a database through: http:// Internet IP Address/adminer

Install the second website(e.g.named mysite2 ), the same steps

Scenario 4: Server Deployment Multiple Websites (Multiple domain)

In the case of no domain, the deployment of two apps as an example, the specific operation is as follows:

  1. Using SFTP to upload your source code directory(e.g.named mysite1) to the default directory: /data/wwwroot
  2. Using Putty to modify the owner of user,just run the fllowing command:
    ~# chown -R apache.apache /data/wwwroot/mysite1
  3. Please complete the domain name resolution(add A record to the Internet IP Address of you Server)
  4. Using SFTP enter to the directory:/ect/httpd/conf.d,add new conf file,assume it’s named is mysite1.conf,then copy the contente below and modify “mydomain,mysite1” to your own values
    <VirtualHost *:80>
    ServerName www.mydomain.com
    ServerAlias mydomain.com
    DocumentRoot "/data/wwwroot/default/mysite1"
    ErrorLog "/var/log/httpd/www.mydomain.com_error_apache.log"
    CustomLog "/var/log/httpd/www.mydomain.com_apache.log" common
    <Directory "/data/wwwroot/default/mysite1">
    Options Indexes FollowSymlinks
    AllowOverride All
    Require all granted
    </Directory>
    </VirtualHost>
  5. Restart the http service
  6. Visit the http://Domain/ to start the application intallation wizard
  7. If you are prompted during the installation wizard database can not be created automatically, you need to create a database through: http:// Internet IP Address/adminer

Install the second website(e.g.named mysite2 ), the same steps

You can run the update command for all the upgrade for this Image

~# yum update -y

Routine backup (archives) of the database and application setup is essential to ensure failover is smooth.

Backup is based on the server snapshot automatic backup and manual local backup in two ways, both of which have their own advantages and disadvantages, it is recommended to use together

Automatic Backup by Snapshot of Server

IaaS provider have the “snapshot” function for Server, the snapshot is for the server disk. Snapshot tool can record the specified point in time the hard disk data, all backed up, and can achieve a key recovery.

If you have an automatic snapshot of the disk settings, the following scenes you can be more calm face:

  • Work a few days of the results, was mistakenly deleted
  • Hackers damage your site
  • The content has been messed up

Done a snapshot backup, a key to restore to the backup point of time state. That is, on-site reduction, very good function.

Different cloud vendor snapshot settings slightly different, specific reference:

Coming soon…

Use domain you should complete the following steps:

Step One:Domain resolution

e.g,If you using the AliCloud Domain product,you should log in to your Domain Console Panel

And find the domain name resolution interface,then add an A record to the Internet IP Address of Server from Domain Control Panel.

Step One:modify the vhost file

  1. Using SFTP to edit the /ect/httpd/conf.d/vhost.conf
  2. Modify the domain related information like below,then save it
    <VirtualHost *:80>
    ServerName www.mydomain.com
    ServerAlias mydomain.com
  3. Using putty to run the command “systemctl restart httpd”

Apache http service

~# systemctl start httpd
~# systemctl stop httpd
~# systemctl restart httpd

MySQL  service

~# systemctl start mysqld
~# systemctl stop mysqld
~# systemctl restart mysqld

When install new extension from back-end it will not successful,may be the permissions of file and folder is not appropriate,you should change it

Web site root permissions to follow:
file 644,folder 755 ,Permissions Users and groups apache,apache
If there is a file permissions problem, execute the following three commands:

~# chown -R apache.apache /data/wwwroot/chyrp
~# find /data/wwwroot/chyrp -type d -exec chmod 755 {} \;
~# find /data/wwwroot/chryp -type f -exec chmod 644 {} \;