Posted in git, linux command, web

Laravel + Git + GoDaddy

1. Configuring SSH and Git

Enable SSH: from cPanel go on Security > SSH Access > Enable SSH, then import your public key.

Check the SSH connection:

# From your local pc 
$ ssh [godaddy-user]@[]

where [godaddy-user] is the username configured for your GoDaddy’s cPanel and [] is the site domain name.

Check that Git is correctly installed on GoDaddy:

$ # From the GoDaddy host 
$ git --version

Create the bin directory on the user’s home:

$ # Always from the GoDaddy host
$ mkdir ~/bin

2. Check the PHP version

Open an SSH connection with GoDaddy, then:

$ php --version

Should print something like:

  PHP 5.5.24 (cgi-fcgi) (built: Apr 20 2015 06:24:55)

Check that the php version is correct (for Laravel 5.1 must be greater than 5.5.9).

Troubleshooting: wrong php version

Can happen that you have setted the newest PHP version from cPanel but via SSH you still have an old version.

If the PHP version is wrong, for example is 5.4.43 instead of 5.5.24, make sure you have changed it in cPanel (in Software > Select PHP Version) then try with:

$ /opt/alt/php55/usr/bin/php --version

If the path /opt/alt/php55/usr/bin/php print out the correct version then set it as your php default command:

$ cd
$ vim .bash_profile

In the file .bash_profile change the row




That is: prepend your local bin directory to assign it the first priority.

Create a link to the right php version:

$ cd bin
$ ln -s /opt/alt/php55/usr/bin/php

Close and reopen the ssh connection and check now the php version.

3. Create the application folder

From GoDaddy host, create the [app] folder in your home, where [app] is the name of your Laravel application:

$ cd ~
$ mkdir [app]

This folder will contains your application.

Depending if you want to install the application in the main domain, e.g., or in a subdomain, e.g., do one of the following.

Main domain

Replace the public_html folder with a symbolic link to [app]/public (be sure public_html is empty before delete it):

$ rm -r public_html
$ ln -s [app]/public public_html


Create a sub domain in GoDaddy


access the cPanel at the url then go on Domains > Subdomains > Create Subdomain and insert:

  • Subdomain: [sub-domain] (e.g. app)
  • Document root: /[app]/public

4. Get Composer

From GoDaddy host:

$ # Install composer
$ cd bin
$ curl -sS | php
$ ln -s ./composer.phar composer

5. Configuring Git for automatic deploy

Create the Git bare repository on the GoDaddy’s host:

$ # Create the git directory where the repository will be mantained
$ cd ~
$ mkdir git

$ # Create the repository
$ cd git
$ git init --bare --shared [app].git

$ # Create the post-receive hook file
$ cd [app].git/hooks
$ touch post-receive

$ # Make the hook executable
$ chmod +x post-receive

$ # Configure the hook
$ vim post-receive

Write in the file post-receive all the operations that will be performed after the push is done:


# Set up our PATH variable and export it
export PATH

# App directories

# Checkout the last commit inside the web app directory
git --work-tree=${APP_WEB_DIR} --git-dir=${APP_GIT_DIR} checkout -f

# Clean the app directory
# Use -e "[pattern]" to exclude some file or directory to be cleaned,
# as they are in the .gitignore file
# git --work-tree=${APP_WEB_DIR} clean -fd

# Run composer
composer install
# Ensure that storage's folder have write permission for the group
chmod -R g+w storage

# Optimizations
echo "Running optimizations"
php artisan config:cache
php artisan route:cache

# Do other things here, for example load database changes automatically
# php artisan migrate
# ...

6. Add the ‘production’ remote in your repository

From your PC:

$ # Go in the project's folder
$ cd /path/to/your/project
# Add the 'production' server's URL
$ git remote add production ssh://[godaddy-user]@[]/~/git/[app].git

Now you can deploy the project on GoDaddy (pushing it on the production remote) with:

$ git push production master

You should now be able to see your code on the folder ~/[app] on the GoDaddy’s host.

After configured the database in the host and configured your application (for example you have to create the .env file in the host and set here the db connection parameters) you will be able to access your application from your domain.


Posted in git, web

Learn Git

Git is the industry-standard version control system for web developers.

  • git init creates a new Git repository
  • git status inspects the contents of the working directory and staging area
  • git add adds files from the working directory to the staging area
  • git diff shows the difference between the working directory and the staging area
  • git commit permanently stores file changes from the staging area in the repository
  • git log shows a list of all previous commits


Git backtrack  allow you to undo changes made to your Git project.

  • git checkout HEAD filename: Discards changes in the working directory.
  • git reset HEAD filename: Unstages file changes in the staging area.
  • git reset SHA: Can be used to reset to a previous commit in your commit history.


Git branching allows users to experiment with different versions of a project by checking out separate branches to work on.

  • git branch: Lists all a Git project’s branches.
  • git branch branch_name: Creates a new branch.
  • git checkout branch_name: Used to switch from one branch to another.
  • git merge branch_name: Used to join file changes from one branch to another.
  • git branch -d branch_name: Deletes the branch specified.


A remote is a Git repository that lives outside your Git project folder. Remotes can live on the web, on a shared network or even in a separate folder on your local computer.

The Git Collaborative Workflow are steps that enable smooth project development when multiple collaborators are working on the same Git project.

  • git clone: Creates a local copy of a remote.
  • git remote -v: Lists a Git project’s remotes.
  • git fetch: Fetches work from the remote into the local copy.
  • git merge origin/master: Merges origin/master into your local branch.
  • git push origin <branch_name>: Pushes a local branch to the originremote.