Git Repository
Bumbled through some git carnage. Set up git tracking for the project. Set up a remote repository on my web host. Had to go back and look at some documentation for how I normally set this stuff up. Questions:
- I have access to my web host as a single user, can’t create another. Can I only then use git (via ssh) as that single user? Can I add another public key that will allow someone else to access the repository, but won’t allow them to log in as me? Or must every git user also have the full access of the web host user?
- If that limitation exists, is this the wrong way to do it. Should this be done with GitHub instead; is that non-free if this is a private repository?
- Is it more sensible to try to set up direct connections between development machines? Seems…shitty.
- Should I look into a different protocol?
- Given how much mental overhead git is, is it even sensible to use it at all?
I always hate dealing with this shit. Just want to build stuff, don’t want to deal with the intricate idiosyncrasies of some auxiliary tool. As a sub-note, it took me about 2 minutes of testing, deleting and retesting to figure out the correct spelling of “auxiliary.”
Time spent: Let’s call it an inconsistent 1h