Git web interfaces should be Bring Your Own, really. I never bother using those as I can have a consistent interface inside emacs. Why should the repository owner choose which interface you view it on?
Self-Hosting Git
21–30 of 71 posts
Re: Self-Hosting Git
#22Interesting! recently I started self-hosting my personal repos using gogs ( https://gogs.io/ ) it’s really lightweight, and I can evn run it in an arm64 box (the same one I use for my NAS). If you’re looking for a more complete yet still lightweight alternative, give gogs a look.
Re: Self-Hosting Git
#23Git web interfaces should be Bring Your Own, really. I never bother using those as I can have a consistent interface inside emacs. Why should the repository owner choose which interface you view it on?
I really don't want to have to pull an entire repo to check something out. I read open source code waaaaaaaaaaay more than I have any need to actually run it or do anything to it locally.
git clone —-depth 1 …Re: Self-Hosting Git
#24Git web interfaces should be Bring Your Own, really. I never bother using those as I can have a consistent interface inside emacs. Why should the repository owner choose which interface you view it on?
I really don't want to have to pull an entire repo to check something out. I read open source code waaaaaaaaaaay more than I have any need to actually run it or do anything to it locally.
Re: Self-Hosting Git
#25Re: Self-Hosting Git
#26It's not really self hosting git. It's self hosting a web interface to git. I swear 90% of people who use git don't know you can just push/pull directly from another computer's git repos.
Re: Self-Hosting Git
#27Probably a naive question, but is a git server required? Could one imagine a git repository stored as static files (e.g. in a cloud bucket), and the client then runs git the functionality. Or, a "serverless" git, with cloud functions? (I guess concurrent writing would be an issue.) EDIT: I don't mean ssh'ing to a server with git installed on it. I was thinking of a git-based protocol but based on static files. But th…
Re: Self-Hosting Git
#28Interesting! recently I started self-hosting my personal repos using gogs ( https://gogs.io/ ) it’s really lightweight, and I can evn run it in an arm64 box (the same one I use for my NAS). If you’re looking for a more complete yet still lightweight alternative, give gogs a look.
Re: Self-Hosting Git
#29Probably a naive question, but is a git server required? Could one imagine a git repository stored as static files (e.g. in a cloud bucket), and the client then runs git the functionality. Or, a "serverless" git, with cloud functions? (I guess concurrent writing would be an issue.) EDIT: I don't mean ssh'ing to a server with git installed on it. I was thinking of a git-based protocol but based on static files. But th…
Simple git server over SSH:
local> ssh example.com
example.com> git init --bare code
example.com> exit
local> git clone example.com:code
Nothing required on the remote side other than an SSH server. Works with multiple users, too - just use SSH auth.Re: Self-Hosting Git
#30Probably a naive question, but is a git server required? Could one imagine a git repository stored as static files (e.g. in a cloud bucket), and the client then runs git the functionality. Or, a "serverless" git, with cloud functions? (I guess concurrent writing would be an issue.) EDIT: I don't mean ssh'ing to a server with git installed on it. I was thinking of a git-based protocol but based on static files. But th…
A long time ago when I was working in a company that still prescribed SVN, I used a backed up network drive location as the location for my git bare repos, I just used it to manage prototypes or feasibility work nothing serious but it was more familiar and productivity for me than the accepted SVN workflow.