Servers Archives - SideCode

Installing Composer Globally on CentOS 7

jhonny — Sun, 03 Sep 2017 10:16:55 +0000

# Installing Composer Globally on CentOS 7

First you need to make sure your system is up-do-date, for that you need to run

yum -y update

Download and install Composer by executing the following command:

curl -sS https://getcomposer.org/installer | php

Once the process completes, you can make the ‘composer.phar’ file executable by running the following command:

chmod +x composer.phar

Now use the following commands to make composer available globally for all users in your system, which can be used for all php applications on that system:

mv composer.phar /usr/local/bin/composer

You can also check the version of composer by running bellow command:

composer -V

And you are ready to go.

The post Installing Composer Globally on CentOS 7 appeared first on SideCode.

Block IP Manually from Fail2Ban Plesk server

jhonny — Tue, 29 Aug 2017 11:43:04 +0000

While using Fail2Ban under a Plesk handled server, you have a GUI to view the current Banned IP’s, and also “whitelist” IP’s (move to trusted IP’s), But you don’t have the option to manually add an IP to the Blacklist, and permanently block a specific IP.

To do so, SSH to your terminal as root.

To see all the Fail2Ban Blacklist IP’s
run (as root):

sudo iptables -nL

To manually block an IP

Run:

sudo fail2ban-client set  banip

Where:

– Is the Jail name.

– Is the ip address you want to ban.

To see your Jail’s run:

fail2ban-client status

To see the list of Banned IP’s Run:

iptables -L -n

In Plesk the common Jail to use is “recidive”

So the command will look like:

sudo fail2ban-client set recidive banip

Be careful not to ban your own IP 🙂

If you do, just switch to your phone network (open an HotSpot) and whitelist your IP (add to Trusted IP’s).

The post Block IP Manually from Fail2Ban Plesk server appeared first on SideCode.

Bitbucket – Setup Git on a Remote Server For an existing Repo

jhonny — Wed, 12 Apr 2017 09:59:03 +0000

Step 1: Switch to your repository’s directory

cd /path/to/your/repo

Step 2: Connect your existing repository to Bitbucket

git remote add origin https://PATH_TO_YOUR_REPO

git push -u origin master

The post Bitbucket – Setup Git on a Remote Server For an existing Repo appeared first on SideCode.

Setting Git on a Production Server

jhonny — Sat, 25 Mar 2017 09:57:42 +0000

To set your git repo on your production server.
go tho the root directory of the server (i.e. public_html or httpdocs etc.)
then run:

git init

run (to connect your server with the cloud repo)

git remote add origin https://PATH_TO_YOUR_REPO

Then if you want your production server to always pull from the remote origin (so you will be able to run git pull instead of git pull origin master)
You need to add this to your /.git/cofig, you can do this like this:

 git config branch.master.remote origin
 git config branch.master.merge refs/heads/master

Now you can run git pull, and it will automatically pull from your master branch.

If you also git to remember your password (so you won’t need to type it with every “git pull”)

enable credentials cache: (make sure you have git version > 1.7.12.1, which you probably have).

git config --global credential.helper cache

The post Setting Git on a Production Server appeared first on SideCode.