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

Normally, installing a python module and its dependencies is done via Pip. If HTTPS is blocked in private networks, then things might get tricky and you get the following message. InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. To bypass this, you can issue the below command to trust pypi.python.org $ pip install --trusted-host pypi.python.org Flask To make sure that the needed module is installed, check it by $ pip freeze

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 OR ii) Add http block in "gitconfig" file to avoid ssl verification [http] sslVerify = false sslCAinfo = /bin/curl-ca-bundle.crt

A useful online calculator to do the size calculation whatsabyte.com Byte Converter

Possible reasons and solutions i) SELinux settings enforcing a file serve $ /etc/selinux/config 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 . (more…)