Skip to main content

Posts

Showing posts with the label repo

Helm: Installation and Configuration

PREREQUISITES You must have Kubernetes installed. We recommend version 1.4.1 or later. You should also have a local configured copy of  kubectl . Helm will figure out where to install Tiller by reading your Kubernetes configuration file (usually  $HOME/.kube/config ). This is the same file that  kubectl  uses. To find out which cluster Tiller would install to, you can run  kubectl config current-context or  kubectl cluster-info . $ kubectl config current-context my-cluster INSTALL HELM Download a binary release of the Helm client. You can use tools like  homebrew , or look at  the official releases page . For more details, or for other options, see  the installation guide . INITIALIZE HELM AND INSTALL TILLER Once you have Helm ready, you can initialize the local CLI and also install Tiller into your Kubernetes cluster in one step: $ helm init This will install Tiller into the Kubernetes cluster you saw with  kubectl config current-context . TIP:  Want to install into a different cl...

Setting your username in Git

Git uses a username to associate commits with an identity. The Git username is not the same as your GitHub username. You can change the name that is associated with your Git commits using the  git config  command. The new name you set will be visible in any future commits you push to GitHub from the command line. If you’d like to keep your real name private, you can use any text as your Git username. Changing the name associated with your Git commits using  git config  will only affect future commits and will not change the name used for past commits. Setting your Git username for  every  repository on your computer Open  Git Bash . Set a Git username: $ git config --global user.name " Mona Lisa " Confirm that you have set the Git username correctly: $ git config --global user.name > Mona Lisa Setting your Git username for a single repository Open  Git Bash . Change the current working directory to the local repository whe...

Setting your username in Git

Git uses a username to associate commits with an identity. The Git username is not the same as your GitHub username. You can change the name that is associated with your Git commits using the  git config  command. The new name you set will be visible in any future commits you push to GitHub from the command line. If you'd like to keep your real name private, you can use any text as your Git username. Changing the name associated with your Git commits using  git config  will only affect future commits and will not change the name used for past commits. Setting your Git username for  every  repository on your computer Open  Git Bash . Set a Git username: $ git config --global user.name " Mona Lisa " Confirm that you have set the Git username correctly: $ git config --global user.name > Mona Lisa Setting your Git username for a single repository Open  Git Bash . Change the current working directory to the local repository where you want to configure the name tha...

Yum : Operation too slow. Less than 1000 byt es/sec transferred the last 30 seconds

First thing to try is the usual yum clean all You might be running 3rd party repositories and do not have yum-plugin-priorities installed. This could compromise your system, so please install and configure  yum-plugin-priorities . You could also try the following: yum –disableplugin=fastestmirror update. minrate  This sets the low speed threshold in bytes per second. If the server is sending data slower than this for at least  timeout' seconds, Yum aborts the connection. The default is 1000′.   timeout  Number of seconds to wait for a connection before timing out. Defaults to 30 seconds. This may be too short of a time for extremely overloaded sites. You can reduce  minrate  and/or increase  timeoute . Just add/edit these parameters in  /etc/yum.conf [main]  section. For example: [main] ... minrate=1 timeout=300

Yum : Operation too slow. Less than 1000 byt es/sec transferred the last 30 seconds

First thing to try is the usual yum clean all You might be running 3rd party repositories and do not have yum-plugin-priorities installed. This could compromise your system, so please install and configure  yum-plugin-priorities . You could also try the following: yum --disableplugin=fastestmirror update. minrate  This sets the low speed threshold in bytes per second. If the server is sending data slower than this for at least  timeout' seconds, Yum aborts the connection. The default is 1000'.   timeout  Number of seconds to wait for a connection before timing out. Defaults to 30 seconds. This may be too short of a time for extremely overloaded sites. You can reduce  minrate  and/or increase  timeoute . Just add/edit these parameters in  /etc/yum.conf [main]  section. For example: [main] ... minrate=1 timeout=300

How to List Files Installed From a RPM or DEB Package in Linux

Have you ever wondered where the various files contained inside a package are installed (located) in the Linux file system? In this article, we’ll show how to list all files installed from or present in a certain package or group of packages in Linux. This can help you to easily locate important package files like configurations files, documentation and more. Let’s look at the different methods of listing files in or installed from a package: How to List All Files of Installed Package in Linux You can use the  repoquery command  which is part of the  yum-utils to list files installed  on a CentOS/RHEL system from a given package. To install and use  yum-utils , run the commands below: # yum update # yum install yum-utils Now you can list files of an installed RPM package, for example  httpd  web server (note that the package name is case-sensitive). The  --installed  flag means installed packages and  -l  flags enabl...

Creating custom YUM repo

This page will be useful when creating your own/ custom yum repo and using it for your yum installations. The standard RPM package management tool in Fedora, Red Hat Enterprise Linux, and CentOS is the yum package manager. Yum works quite well, if a little bit slower than other RPM package managers like apt4rpm and urpmi, but it is solid and handles dependencies extremely well. Using it with official and third-party repositories is a breeze to set up, but what if you want to use your own repository? Perhaps you manage a large computer lab or network and need to have — or want to have — certain packages available to these systems that you maintain in-house. Or perhaps you simply want to set up your own repository to share a few RPM packages. The following are the steps to create your own repo. Step-by-step guide Follow these steps on server machine. Creating your own yum repository is very simple, and very straightforward. In order to do it, you need the  createrepo ...