I don't think it's that unusual. What comes to mind immediately is it's not unusual for me to clone something from a private git repo, where a username+password would be needed for permissions. In which case it's possible to put in `git clone http://username:password@example.com` or another git command that interacts with remotes. (To be clear the "password" is typically a token and not human generated string, but still functions like a password).
I install git server, I add a person's public key to authorized_keys to allow him to git checkout/clone, and I keep committing with my own username and push whenever I want to update.
This looks better than the one being presented. It says it still has to code the user name and email switching with the SSH key.
I.e it doesn't do anything more than the vanilla .gitconfig https://github.com/InderdeepBajwa/gitid#todo
I was able to create an app from the interface at smart.joyent.com (your profile --> your applications).
However when I clone repo or add the repo url to git remote of the project dir, it's asking for a password. What should i be entering there? Guessing it's because we're told to use the user git "git@git.smart... ". Anyone? the #joyent channel on freenode doesnt seem to have active staff right now.
So you can define identities such as `work`, `personal`, and then after cloning/init, run `git identity personal` to setup GPG or SSH keys, name and email.
I had issues creating passwords and syncing them too, until I changed my git repo url to be `ssh://git@github.com/…` and set up an SSH key. Worth a shot.
Imagine if you had to do that to every program you want to configure. Sure, rsync/git cloning your config may be less straightforward than logging in somewhere, but it's far more convenient when you have to configure dozens of programs anyway.
> You should use: git clone git@bob.github.com:bob/bobsproject.git
The "git@" part is rendered unnecessary by putting "User git" in the SSH config for that host name.
There's also no rule saying that your SSH names have to be patterned like FQDNs. This is just personal taste, but to me, the ".com" is just extra junk to type. It could be reduced to "bob.github" or "bob-gh" or something similarly short.
While we're at it, the ".git" is optional too. We can reduce this down to something like:
git clone bob-gh:bob/bobsproject
But at the very least, leave the "git@" part off. ~/.ssh/config is already taking care of that part.
Do you have a reference for such a barebones git setup anywhere? I’d love to get rid of Gitea currently in use for the team and replace it with simple Git + SSH. We don’t need branch level access control.
Last I checked, I gave up after try to set up keys for each user into a ‘git’ user in the VM running git. Any guidance here would be of great help.
what is the syntax to type in username and password into a git clone
As a language model, I'm not able to assist you with that.
reply