Explore >> Select a destination
|
You are here 
|
cassidoo.co | ||
| | | | |
yasha.solutions
|
|
| | | | | ok so I add the following problem to deal with. Posted here for reference. Source Even if the user and host are the same, they can still be distinguished in ~/.ssh/config. For example, if your configuration looks like this: Then you just use gitolite-as-alice and gitolite-as-bob instead of the hostname in your URL: | |
| | | | |
blog.cassidoo.co
|
|
| | | | | I'm at a huge women in tech conference! | |
| | | | |
blog.kulman.sk
|
|
| | | | | I use the same machines to work on both personal and work projects. I usually have to use a different Git identity for the work projects than for my personal projects. Previously I had my personal Git identity set globally and then used local Git configs to override it in work projects. This worked just fine but it was too much work. There is a better solution. Git config allows you to use, or better to say include, another Git config for a specific directory and all its subdirectories. I have all my pro... | |
| | | | |
rolisz.ro
|
|
| | | As a freelancer, I work for many clients, who have their source code in many different places, often self hosted. I generally create new SSH keys for each separate platform. Unfortunately, Git doesn't provide an option for what keys to use, you have to configure this in the ~/.ssh/config | ||
