nasirkhan

Sometimes we need to keep a file in the project but do not want to track the changes, for example the config/configuration file or other setting file.

git has a solution to do this. First change the file you do not want to be tracked and use the following command.

git update-index --assume-unchanged FILE_NAME

and if you want to track the changes again use this command,

nasirkhan

You have existing.zip but want to split it into 50M sized parts.

zip existing.zip --out new.zip -s 50m

will create

new.zip

nasirkhan

<?php

/**
 * 
 * GIT AUTO DEPLOYMENT SCRIPT
 * 
 * GITHUB? GITLAB webhook
 * -------------------------------
 *
 */

nasirkhan

/**
*
*    Input any number in Bengali and the following function will return the English number.
*
*/

function bn2enNumber ($number){
    $search_array= array("১", "২", "৩", "৪", "৫", "৬", "৭", "৮", "৯", "০");
    $replace_array= array("1", "2", "3", "4", "5", "6", "7", "8", "9", "0");
    $en_number = str_replace($search_array, $replace_array, $number);

nasirkhan

<?php

php artisan tinker
$controller = app()->make('App\Http\Controllers\MyController');
app()->call([$controller, 'myMethodName'], []);

//the last [] in the app()->call() can hold arguments such as [user_id] => 10 etc'

nasirkhan

git discard all local changes/commits and pull from upstream

git reset --hard origin/master

git pull origin master

nasirkhan

First, you should ensure that your username is included in www-data group. If not, you can add your username as www-data group

sudo adduser $USER www-data

After that, you should change the ownership of /var/www to your username

sudo chown $USER:www-data -R /var/www

Next step, you should change permission to 755 (rwxr-xr-x), not recommend changing permission to 777 for security reason

nasirkhan

# initialization file (not found)

nasirkhan

```
#!/bin/sh
for file in `ls *.html`
do
newname=`echo $file|sed 's/\.html$//g'`
mv $file $newname
done
```

nasirkhan

SSH Keys

SSH keys provide a more secure way of logging into a virtual private server with SSH than using a password alone. While a password can eventually be cracked with a brute force attack, SSH keys are nearly impossible to decipher by brute force alone. Generating a key pair provides you with two long string of characters: a public and a private key. You can place the public key on any server, and then unlock it by connecting to it with a client that already has the private key. When the two match up, the system unlocks without the need for a password. You can increase security even more by protecting the private key with a passphrase.

https://www.digitalocean.com/community/tutorials/how-to-set-up-ssh-keys--2

Step One—Create the RSA Key Pair

The first step is to create the key pair on the client machine (there is a good chance that this will just be your computer):