Installation

You can learn how to install phalcon slayer, how to initially setup your environment.

Installation

You can learn how to install phalcon slayer, how to initially setup your environment.

Index:

• Requirements
  • Basic
  • For Queuing
• Project Creation
• Dot Environment
• Web Server

Requirements:

Before installing, there are plenty of packages that we need to install first:

Basic requirements:

• PHP version atleast 5.5.9
• Phalcon Extension
• Composer
• cURL

For Queuing:

• You are required to install Beanstalkd

Most of these packages are already installed on your favorite os box.

---

Project Creation:

Using composer, you can create a new project, write this code on your terminal:

Shell

composer create-project phalconslayer/slayer --prefer-dist <folder name>

After running this command, there should be an output, similar below:

Shell

Installing phalconslayer/slayer (version)
  - Installing phalconslayer/slayer (version)
    Downloading: 100%

Created project in folderName
> php -r "copy('.env.example', '.env');"
Loading composer repositories with package information
Installing dependencies (including require-dev)

---

Dot Environment:

Let us say we have a local / staging / production servers. The local comes with multiple developers, however we don't want our developers to view those passwords or we call it "credentials", such as our production database, mail credentials, aws access token and many more.

On your project we have the ".env.example", let's copy this file and name it as ".env". Furthermore, this file handles a global constant value, let us say we have this:

Shell

DB_HOST=192.168.10.10

You can access the constant value DB_HOST by using the function env(<constant name>, <default value>)

Try to check the file config/database.php, and find the env('DB_HOST', 'localhost'), if there will be no value in our source, it will be based on the default value which is localhost

Note:
This file is already ignored under your GIT Distributed Version Control

Web Server

Slayer has configurations for Apache2 and NginX, it is located at:

• project-name/storage/etc/nginx/sites-available/
• project-name/storage/etc/apache2/sites-available/

we have an example slayer.app file for both web server, you could copy the file and put it in your web server sites-available or you could apply a Symlink.

Let us say we have an NginX under UbuntuOS:

Shell

cd /etc/nginx/sites-enabled/
ln -s ../../../var/www/phalconslayer/slayer/storage/etc/nginx/sites-available/slayer.app
sudo service nginx restart

The command above shows that you must be located at the nginx sites-enabled and you must call the command ln -s to apply symlink. We've also restarted the nginx server.

Add a domain on your /etc/hosts file and point it to your local IP, you should be able now to access your website.

To check that, you can try this cURL command:

Shell

curl -v -s slayer.app 1> /dev/null

The curl command above must return this kind of format:

Shell

* Connected to slayer.app (192.168.10.10) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.35.0
> Host: slayer.app
> Accept: */*
>
< HTTP/1.1 200 OK
* Server nginx/1.8.0 is not blacklisted
< Server: nginx/1.8.0
< Date: Thu, 03 Mar 2016 00:45:27 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: slayer=ojoo6udniihctp11hcjh1hcll3; path=/
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Pragma: no-cache