/explore
|
You are here 
|
embeddeduse.com | ||
| | | | |
blog.slackware.nl
In an earlier article here on the blog, I documented how I have setup cgit to create a browseable web interface to my git repositories, most notably git.liveslak.org and git.slackware.nl. That conf... |
|
| | | | | ||
| | | | |
werat.dev
If you often use ssh+tmux combination and ssh keys forwarding, you've definitely been in an unpleasant situation: connect to some remote machine via ssh and create a tmux session use it happily detach from tmux and disconnect from server connect again (e.g. next day) and attach to the tmux session push something to git (or connect to another server)... ... Permission denied (publickey). Let's discuss why this is happening. The magic behind ssh forwarding is quite simple: ssh-agent creates a socket (on linux usually something like /tmp/ssh-hRNwjA1342/agent.1342) which is used by other applications to communicate with ssh-agent. Obviously these applications need a way to find this socket, so ssh-agent also sets an environment variable SSH_AUTH_SOCK, which cont... |
|
| | | | | ||
| | | | |
adventures.michaelfbryan.com
When developing locally, you can add a private GitHub repository to your Rust crate as a git dependency and cargo should be able to retrieve it just fine. However, when you push your changes to GitHub and run CI, GitHub Actions can run into authentication issues when trying to build your crate. This is the error message I was fighting for a good part of today: $ cargo check --workspace --verbose --locked Updating git repository `https://github. |
|
| | | | | ||
| | | | |
navendu.me
A practical + interactive crash course on Git (that slaps). |
|
| | | |||
