Hacker News Reader

Comment by aphextron | Hacker News Reader

This looks promising. Can't wait to check out the source. How exactly do you plan on monetizing while allowing unlimited free private repos?

Also, for anyone looking for a good self-hosted git service like this, check out the existing open source project GOGS https://gogs.io/

View on HN

Hosting on gitly.io for $1/user/month (if more than 5 users).

For self-hosting maybe I'll go the GitLab route, which I don't really like. I think the product should have the same set of features for all customers. Maybe I'll just go for paid extended support. We'll see.

I've thought about this in the past, and I would do something where features are delayed 6 months to a year to the community version.

i have generally seen that a piece of software that is built for self-deployment is not optimized for scalability. in fact, optimizing for scalability screws around with ease of deployment.

It will be interesting to see you pull this off if you are indeed thinking of making your software dual purpose - self deploy as well run a scaleable/fault-tolerant hosting company.

You are right, these are two very different tasks. That's what makes solving this fun and challenging. I had it in mind when I was designing the architecture of gitly. In the end it really is going to be easily deployed and scalable.

I would recommend to use gitea.io it's a gogs fork that far a better open-source project, that gogs maintainer weren't too active at some point

I've been following both projects with quite some interest and it looks like gogs has become much more active, now a days. Here's a quick break down on both projects:

3 months of commits activity:

https://gitsense.com/gogs-gitea-analysis/commits-3months.png

6 months of commits activity that only unique commits between gitea and gogs.

https://gitsense.com/gogs-gitea-analysis/commits-6months-uni...

September was when things started to slowly deviate, between the two projects, and November was when gitea really went off on their own. At around January, gogs started to pick up steam and has continued on an upward trajectory ever since.

This is what it looks like, if you want to merge gitea, back to gogs.

https://gitsense.com/gogs-gitea-analysis/merge-gitea-to-gogs...

You are looking at 3,201 changes that needs to be resolved.

This is what moving gogs to gitea looks like.

https://gitsense.com/gogs-gitea-analysis/merge-gogs-to-gitea...

Going this way, you'll only have to resolve 1,244 changes.

These are the contributors to gogs, within the last 3 months.

https://gitsense.com/gogs-gitea-analysis/gogs-contributors-3...

Contributions to gitea, within the last 3 months.

https://gitsense.com/gogs-gitea-analysis/gitea-contributors-...

The contributions information, better highlights why gitea forked, since for gogs, virtually all changes, goes through u@gogs.io

Reply on news.ycombinator.com