If you want to add certain files that was previously removed from Git repository, follow the steps given below.
STEP 1: remove the file reference in .gitignore
STEP 2: remove the cached reference from git.
$ git rm –cached sampleconfig.txt
As a developer, you may come across scenarios when you think that certain SPECIAL files should not be tracked in Git commits.
As the first step, commit all changes in your repository and then add those SPECIAL files to .gitignore
To remove a file (not delete) from getting tracked in your Git repository use:
$ git rm –cached sampleconfig.txt
To remove all files that is referenced in your .gitignore use:
$ git rm -r –cached .
Solution is to use Node Version Manager (nvm) which helps manage multiple version of node versions.
$ curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.31.0/install.sh | bash
To see the list of all available nvm versions,
$ nvm ls-remote
Currently, Node v6.11.1 has the long term support (Latest LTS: Boron). We will setup that first version
$ nvm install 6.11
The above command will install Node.js version 6.11.x (where x will be the last available version number)
To find where the node version is installed, type
$ nvm which 6.11
As of this writing, the latest version available is v8.1.4
$ nvm install 8.1.4
When nvm installs the corresponding npm package also gets installed.
You can switch between different versions of the node by typing
$ nvm use 6.11.1
$ nvm use 8.1.4
To list all the available versions of installed node versions, type
$ nvm ls
When atom installs, it sets up a symbolic link to the location where it is installed. You can open a file or folder in atom by using the following commands
a) Open the editor
b) Open a file
$ atom index.html
c) Open atom in the current folder
$ atom .
First checkout Develop branch
$ git checkout dev
Then, reset it to Master branch
$ git reset –hard master
Make sure to push the changes by force to make origin/dev to be the same as origin/master
$ git push –force origin develop
Point 1) Check if you have followed the below sequence of steps when setting up git in your local workstation
$ git init
$ git add .
$ git commit -am “name of the commit”
$ git remote add origin https://github.com/username/repository.git
$ git push -u origin master
Point 2) Check if .git/config file has the following parameters in it[branch “master”]
remote = origin
merge = refs/heads/master
Git uses “Transfer-encoding” in POST requests and some proxy servers do not support this encoding by default. When large files are pushed, the git client requires higher http.postBuffer setting.
Increase the buffer size to see if the issue is related to it.
$ git config –global http.postBuffer 134217728
You get this message when the system is behind a firewall and when the security certificates are blocked.
There are two ways to overcome this message and to enable a git pull or git clone.
i) Issue the below command from git bash
$ git config –global http.sslVerify false
ii) Add http block in “gitconfig” file to avoid ssl verification[http] sslVerify = false
Possible reasons and solutions
i) SELinux settings enforcing a file serve
Change SELINUX = disabled within the file and check if this is the cause for the error
ii) Application directory under restricted user permission folder path
For example, configuring the django project inside /root folder and trying to serve those files via apache server (apache user).
Try changing the folder to a path that you think is good for allowing public access such /var/www or /opt/sites .