Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Self-hosted Git Server

petekeen.net

Post reply on HN
Print view View original

51–60 of 62 posts

Re: Self-hosted Git Server

#51

Post by zrail »

camus2 wrote: post #45
zrail wrote: post #24

Earlier quoted context omitted.

Life is built of tradeoffs and compromises. For you, github pages makes total sense. For me, not so much. Saying that my little VPS is "grossly inefficient" compared to your GitHub repositories is like comparing apples to... I dunno, like a rock? or a monkey? Something else entirely, that's for sure.

It only proves you did not build your solution with scalability in mind. Once you get more traffic and the hosting bill goes up, i'm pretty sure you'll reconsider self hosting for the sake of self hosting.

The page in the original post has received 16,000 pageviews in the last 12 hours. Admittedly the project pages were not performing very well initially but after I added caching they haven't even blinked, and the dual core VPS (which runs a dozen other services besides this) is ticking along at a load average of 0.63.

Tell me again how I didn't design for scalability. I'd also love to hear your definition of "more traffic".

Re: Self-hosted Git Server

#52

Post by edwintorok »

616c wrote: post #30

I checked out this guy's site. I understand he is reinventing the wheel. I respect that and do not mean anything negative about that. A lot of us are here to understand the wheel and build for ourselves. There is good value for that. What I do not understand, with all due respect, is the value of Github, and to a lesser extent Bitbucket, is in the features outside of the VCS core and how most people realize there is…

I don't consider Github's issue tracker to be particularly good.

Sure its convenient if you just have a small project and don't want to host an issue tracker yourself and don't care about the usability of the issue tracker.

The "killer feature" of the issue tracker is that you don't need to create yet another login just to report a bug. Chances are you've reported an issue on github before, or if not you just have to create a user once, that you can use to report bugs on any github project.

I consider Github's issue tracker to be a significant step backward/in the wrong direction from Bugzilla for several reasons:

  * defaults to markdown instead of plain text [1]

  * no easy way to attach binary files[2]

  * no easy way to attach files[3]
At least from a project developer's perspective I find bugzilla much easier to use (once you get used to it), and has more features.

There are some minor improvements in Github's issue tracker, but none that would want to make me switch.

[1] Whenever I paste some error message / shell output I need to escape it in 

 or  blocks, otherwise it messes up the formatting. I initially created a lot of broken bugreports, that I had to edit once I've seen how bad it looked, of course then I found out you can preview the bug before submitting. IMHO text should be the default for bugreports, not markdown!
[2] they come in handy depending on the project. If the project deals with binary files, it is expected that bugreports may have to contain them as well
[3] Besides creating a gist and pointing to the gist you pretty much have to self-host any file you want to "attach" to a Github issue, unless I'm missing something.

Re: Self-hosted Git Server

#53

Post by zrail »

mixologic wrote: post #36

What about all the problems that are inherent to hosting anything ? It's not hard to set up a server that will respond to a request and deliver data. It's hard to make it do that when the power goes out, when you anger somebody and they decide to ddos you, or when your code/service/whatever becomes insanely popular and whatever mac mini you run it on is overheating. It's hard to keep up with all the security patches…

I'm sorry, I should have clarified. My private repos are running on a VM in the living room, but the public-facing website and repos are all on a Digital Ocean VPS.

Re: Self-hosted Git Server

#54

Post by 616c »

bgarbiak wrote: post #43
616c wrote: post #30

I checked out this guy's site. I understand he is reinventing the wheel. I respect that and do not mean anything negative about that. A lot of us are here to understand the wheel and build for ourselves. There is good value for that. What I do not understand, with all due respect, is the value of Github, and to a lesser extent Bitbucket, is in the features outside of the VCS core and how most people realize there is…

What about Attlassian's JIRA + Stash + Confluence combo?

For anything I see as really important these days, I avoid anything that is not open source. It used to be idealism, but now I see it as practicality. If something happens to Atlassian, I am up a creek. I will call this the Perforce Scenario (for the resulting problem, not the originating issue), because Perforce revoked its exception to its proprietary SCM when a Linux contributor reverse engineered it for an open source client he wanted to use with it, violating the terms.

So Atlassian might be free for open source projects (they say for Stash at least after Googling), but that can always change with any app or service you use. RMS free should not change, and you should be able to understand the most current copy you have of source to find alternatives or build your own. Fortunately, this rarely happens for the core FOSS items I use. I have been lucky.

Also, Atlassian can be pretty hefty for small weekend projects in my opinion. But I have only used Confluence at work, it seems like it would require much more resources than a server or VPS for weekend projects would require. I could be wrong.

Re: Self-hosted Git Server

#55

Post by showerst »

geerlingguy wrote: post #18

Here's another example, using Ansible and a few simple roles from Ansible Galaxy: https://github.com/geerlingguy/ansible-vagrant-examples/tree... Give Vagrant + Ansible about 15 minutes, and you'll have a nice little local GitLab server running. Modify the Ansible playbook slightly, to point it at a VM on Digital Ocean or elsewhere, and you'll have a nice little hosted copy of something like GitHub. I run an instance…

I prefer ansible too, but FWIW DigitalOcean has a pre-configured gitlab droplet as well. You can literally have it live in < 5 minutes, including registering and configuring a domain.

Re: Self-hosted Git Server

#56

Post by jpiasetz »

edwintorok wrote: post #52
616c wrote: post #30

I checked out this guy's site. I understand he is reinventing the wheel. I respect that and do not mean anything negative about that. A lot of us are here to understand the wheel and build for ourselves. There is good value for that. What I do not understand, with all due respect, is the value of Github, and to a lesser extent Bitbucket, is in the features outside of the VCS core and how most people realize there is…

I don't consider Github's issue tracker to be particularly good. Sure its convenient if you just have a small project and don't want to host an issue tracker yourself and don't care about the usability of the issue tracker. The "killer feature" of the issue tracker is that you don't need to create yet another login just to report a bug. Chances are you've reported an issue on github before, or if not you just have to…

This is an interesting comment, my work flow is almost completely different. I wonder if it's a difference based on what language we both spend the majority of our time in (for me Javascript, python, ruby).

* For markdown I prefer the synatx highlighting and scrollbars that show up on github to the giant blobs plain text gives you.

* I rarely want to attach binary files while I often find myself embedding inline images to illustrate a point

* I use cat test | gist -c -f test.txt -d "Output from failure" (it puts the gist link in my clipboard).

Re: Self-hosted Git Server

#57

Post by coherentpony »

edwintorok wrote: post #52
616c wrote: post #30

I checked out this guy's site. I understand he is reinventing the wheel. I respect that and do not mean anything negative about that. A lot of us are here to understand the wheel and build for ourselves. There is good value for that. What I do not understand, with all due respect, is the value of Github, and to a lesser extent Bitbucket, is in the features outside of the VCS core and how most people realize there is…

I don't consider Github's issue tracker to be particularly good. Sure its convenient if you just have a small project and don't want to host an issue tracker yourself and don't care about the usability of the issue tracker. The "killer feature" of the issue tracker is that you don't need to create yet another login just to report a bug. Chances are you've reported an issue on github before, or if not you just have to…

Don't forget that the conversation on tickets is forced to be linear. Nested replies are not possible.

Re: Self-hosted Git Server

#58

Post by edwintorok »

jpiasetz wrote: post #56
edwintorok wrote: post #52

Earlier quoted context omitted.

I don't consider Github's issue tracker to be particularly good. Sure its convenient if you just have a small project and don't want to host an issue tracker yourself and don't care about the usability of the issue tracker. The "killer feature" of the issue tracker is that you don't need to create yet another login just to report a bug. Chances are you've reported an issue on github before, or if not you just have to…

This is an interesting comment, my work flow is almost completely different. I wonder if it's a difference based on what language we both spend the majority of our time in (for me Javascript, python, ruby). * For markdown I prefer the synatx highlighting and scrollbars that show up on github to the giant blobs plain text gives you. * I rarely want to attach binary files while I often find myself embedding inline imag…

Majority of my bugreports are related to C/C++ and to some extent OCaml, and mostly command-line programs. Hence a text-based entry for the bugreport is more convenient.

Re: Self-hosted Git Server

#59

Post by rsgalloway »

heh, what at the odds: two libs that give you object-oriented access to git repos both coincidentally named the exact same thing:

python: github.com/rsgalloway/grit ruby: github.com/mojombo/grit

Re: Self-hosted Git Server

#60

Post by lholden »

_frog wrote: post #13
lholden wrote: post #9

The fantastic thing about distributed version control systems like GIT is that you never actually have to depend on a single repository. Use Github, Bitbucket, and your own "server" all at once. None have to be read-only. Push and pull from multiple sources. Decide that Github is no longer the place for you? No problem! People contributing to your projects should already know where to push to reach everywhere it need…

Worth noting though, a lot of the value of GitHub in particular, and to a lesser extent many other services, are extra features like issue trackers, wikis and so on that act to lock you in.

I can certainly see services like wiki and issue tracker hosting being big value-adds with GitHub. Thankfully GitHub does allow you to export your data. (And to be honest, I feel it would be a mistake to use these services if you couldn't export your data.)

The wiki system on GitHub is based out of it's own git repo (https://github.com/[user]/[repo].wiki.git). If you could be bothered to pull/push when changes are made, I'd imagine this content could then be made distributed.

While not distributed/decentralized... GitHub does lets you export your existing issues. The resulting archive can then be imported into services like bitbucket, pivotal, and etc with a little work.

There are solutions for distributed/decentralized issue tracking, but I haven't seen any great way for users to interact with them. (SD and Bugs Everywhere, other users have posted links in their replies.)

Post reply on HN