sudo chown -R www-data:www-data folder_name
sudo chmod 775 -R folder_name

MySQL has system timezone, global timezone and session timezone (also call as per request timezone).

System timezone is current machine's timezone.
Global timezone and session timezone default value is system timezone.

When user insert a value to timestamp column (we call "date1"), MySQL suppose date1 as session timezone and convert to global timezone then save to DB.

When user select timestamp column, MySQL will convert from global timezone to session timezone than return value.

Open git command line of current repository and run:

git config credential.helper store

Note: you may need to enter password onetime again.

Environment:

• Window 10 Home
• Docker toolbox
• Proxy set in internet options

Problem:

1. Docker can not pull images.
2. Container can not connect to internet.

Solution:

To fix problem 1

Step1: remove your default machine

docker-machine rm default

Step2: recreate your default machine with proxy

docker-machine create -d virtualbox --engine-env HTTP_PROXY=http://your_proxy_url:your_proxy_port default

if that not working, you may try this option instead.

docker-machine create -d virtualbox \
    --engine-env HTTP_PROXY=http://example.com:8080 \
    --engine-env HTTPS_PROXY=https://example.com:8080 \
    --engine-env NO_PROXY=example2.com \
    default

To fix problem 2

Create or edit the file ~/.docker/config.json in the home directory of the user which starts containers.

{
 "proxies":
 {
   "default":
   {
     "httpProxy": "http://your_proxy_url:your_proxy_port"
   }
 }
}

Then restart ... computer and rebuild any thing.

Why compatibility view mode ?

Some old sites are created to work with old versions of IE. For example, your site only work with IE7, so if I open your site in IE11, I will get some issues (such as misaligned text, images, or text boxes, issues with scripts, and some crash situations)

To fix, I need to set your site in compatibility view list in my IE (Tools -> Compatibility View settings), IE will show your site using older IE versions (IE will detect which version suitable for your site), and make it work.

In other hands, if your site is created to work with latest IE version (IE11 for now), and for some reason, i was set your site in compatibility view list, it may get some issues also.

In this case, I need to remove your site from compatibility view list, IE will show your site using latest IE version by default.

How to fix automatically ?

As above, in both cases, you should set your default IE version for your site to work, by adding this meta tag to your pages. This tag must be placed before any other meta tags for it to work.

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7"> <!-- to force it work with IE7 -->
or
<meta http-equiv="X-UA-Compatible" content="IE=edge" /> <!-- to force it work with latest IE version -->

If this tag was set, IE will show your site with point out IE version, and do not care if i set your site in compatibility view list or not.

If you would like to make this change throughout your site and do not want to edit every page edit your .htaccess file and add the below lines into that file.

# Emulate IE7 to prevent compatibility view
BrowserMatch "^.*MSIE 8.*$" emulate_ie7
Header set X-UA-Compatible "IE=EmulateIE7" env=emulate_ie7
or
# Emulate edgeto prevent compatibility view
BrowserMatch "^.*MSIE 8.*$" edge
Header set X-UA-Compatible "IE=edge" env=edge

1. dependencies

Suppose, you create a javascript package name your-package and release a your-package.js file.

And Bob (someone) want to use your-package.js in his project name bob-project. Then Bob install your-package via npm:

npm install your-package

But your-package.js required lodash 1.0.0 to work with.

'use strict';

var _ = require('lodash');

// call some lodash functions

so if Bob want to use your-package.js then he must have lodash 1.0.0 somewhere in bob-project.
And because of Bob only care about your-package.js, it painfull for Bob to install lodash 1.0.0 manually.

In this case, you should define lodash 1.0.0 as your-package dependency, inside package.json file:

"dependencies": {
  "lodash": "1.0.0"
}

# Note 1
You may need lodash 1.0.0 as well to run test. So you should install lodash via npm:

npm install lodash@1.0.0

npm will automaticlly add dependency lodash 1.0.0 to package.json file.

Now if Bob install your-package, npm automaticlly install lodash 1.0.0 along with it.
bob-project folder structure is like:

bob-project/
├──node_modules/
│  ├──your-package/
│  └──lodash/              # version 1.0.0
├──package-lock.json
└──package.json

# Note 2
If already have other version of lodash (ex 2.0.0) installed before Bob installing bob-project, folder struct will become:

bob-project/
├──node_modules/
│  ├──your-package/
│  │  └──node_modules/
│  │     └──lodash/        # version 1.0.0
│  └──lodash/              # version 2.0.0
├──package-lock.json
└──package.json

when execute require, nodejs will search modules from current folder first, if package can not be found nodejs will find package in parent folder an so on, so your-package.js will get lodash 1.0.0, separate with lodash 2.0.0. Everything still work!

2. devDependencies

To create your-package you may need some task-runner like gulp, for example to concat all js file into one. So you install gulp via npm:

npm install gulp

By this way (# Note 1 above), npm will add gulp to dependencies, and Bob will get automaticlly install gulp that he does not need to run your-package.js.

In this case, you should define gulp as "devDependencies" by install gulp with --save-dev:

npm install gulp --save-dev

your package.json will be like:

"dependencies": {
  "lodash": "1.0.0"
},
"devDependencies": {
  "gulp": "^3.9.1"
},

Now when Bob install your-package, npm does not care about "devDependencies" and Bob only get lodash be installed.

3. peerDependencies

If your-package actually is a grunt plugin for example, your-package.js file will be like:

'use strict';

var _ = require('lodash');

module.exports = (grunt) => {

  // call some lodash functions

  // use grunt instance to do some small stuff to support main grunt function
}

Without require('grunt'), it's using host grunt package instance (the package installed in bob-project). That mean your-package still need grunt for running, and like "1. dependencies" above it may need to automaticlly install grunt as dependencies.

But, because of your-package is a grunt plugin so maybe Bob has already installed other version of grunt in bob-project, therefore a version of grunt will be automaticlly installed inside your-package folder structure (# Note 2) and would never be used, that is not good.

So your-package should not automaticlly install grunt. By this way you need to tell Bob (when he's installing your-package) that he need grunt for your-package, moreover which version of grunt that your-package can run with. To do this, you need peerDependencies!

You define grunt as peerDependencies like this:

"dependencies": {
  "lodash": "1.0.0"
},
"devDependencies": {
  "gulp": "^3.9.1"
},
"peerDependencies": {
  "grunt": "0.4.2"        # suppose that your-package only work with 0.4.2
},

Now when Bob install your-package, he will get a warning that he need to manually install grunt 0.4.2.

Yes, peerDependencies is just for giving warnings, nothing else!

Event if your-package using direct dependency like lodash 1.0.0 (1.0.0 is lasted version of lodash when you create your-package). But now lodash release 2.0.0 with many great features, using your-package with lodash 2.0.0 would great, and you too lazy to test and update your-package. In this case, you would consider to define lodash in peerDependencies like this:

"dependencies": {
},
"devDependencies": {
  "gulp": "^3.9.1"
},
"peerDependencies": {
  "grunt": "0.4.2"        # suppose that your-package only work with 0.4.2
  "lodash": ">=1.0.0"     # 1.0.0 or newer
},

Now when Bob install your-package, he just manually install lodash 2.0.0 to work with.

Why not define direct dependency to automaticlly install lodash 2.0.0 like this ?:

"dependencies": {
  "lodash": ">=1.0.0"     # 1.0.0 or newer
},
"devDependencies": {
  "gulp": "^3.9.1"
},
"peerDependencies": {
  "grunt": "0.4.2"        # suppose that your-package only work with 0.4.2
},

Because in case of your-package can not work with lodash 2.0.0 due to removed APIs (you can not test in time when lodash 2.0.0 release), your-package in bob-project will brocken.
If you using peerDependencies, after manually installed lodash 2.0.0 and realize that issues, Bob can rollback to lodash 1.0.0 to make your-package work. Fine!

# Preferences

# Peer Dependencies
# Understanding the npm dependency model
# Why use peer dependencies in npm for plugins?
# Semantic Versioning
# Specifics of npm's package.json handling
# Requiring modules in Node.js: Everything you need to know

1. Download package

Open terminal and run follow command:

wget url_of_compressed_file

2. Extract file

If it's tar.gz use

tar xvzf file_name.tar.gz

If it's a tar.bz2 use

tar xvjf file_name.tar.bz2

3. Go to extracted folder and run follow command

./configure

make

sudo make install

Sometime we just want to ignore one specific warning in specific file.

1. Open Problems tab: Window -> Show View -> Problems.

2. Find that warning and right click -> Delete.

1. Downloading and installing VirtualBox manually

https://www.virtualbox.org/wiki/Downloads

2. Downloading and installing Vagrant manually

https://www.vagrantup.com/downloads.html

3. Installing The Homestead Vagrant Box

$vagrant box add laravel/homestead

This is a virtual machine image that runs the operating system.

4. Installing Homebrew (global)

https://brew.sh/

5. Installing Composer via Homebrew (global)

$brew install composer

open ~/.zshrc (if using zsh, or whatever bash profile file we using) and add this to end of file:

export PATH="$PATH:$HOME/.composer/vendor/bin"

we need to reopen terminal.

6. Installing Lumen installer (global)

$composer global require "laravel/lumen-installer"

7. Create new Lumen project

$lumen new NEW_PROJECT

8. Installing Homestead (local)

Go to NEW_PROJECT folder and run this command:

$composer require "laravel/homestead"

This is configurations repo which are used when running homestead virtual machine image.

init Homestead

$php vendor/bin/homestead make

Homestead.yaml will be created like below:

ip: 192.168.10.10
memory: 2048
cpus: 1
provider: virtualbox
authorize: ~/.ssh/id_rsa.pub
keys:
    - ~/.ssh/id_rsa
folders:
    -
        map: #your new project dir
        to: /home/vagrant/code
sites:
    -
        map: homestead.test
        to: /home/vagrant/code/public
databases:
    - homestead
name: NEW_PROJECT
hostname: NEW_PROJECT

9. Config

Add this line to host file /etc/hosts

192.168.10.10 homestead.test

10. Run

Start virtual machine

$vagrant up

and access via browser

http://homestead.test/