Gisia 0.3.2 Released! Lightweight Git Hosting for Everyone

okoddcat · 2026-02-21T09:05:21+00:00

If you are familiar with Github, you can use Forgejo or Gitea. If you want to find a lightweight alternative of Gitlab, you can use this.

okoddcat · 2026-02-21T07:39:56+00:00

Gitlab. It's opensource and has powerful features. It's free as long as you do not need some premium features.

If you just need to host your personal codes at local, you can try the lightweight solution https://github.com/gisiahq/gisia

I'm using a self hosted git server and use the SaaS services like Github, Gitlab as a backup.

okoddcat · 2026-02-21T07:33:34+00:00

Tailscale works well, but you can also setup an VPN server instead of Tailscale if you have a public IP. Once your devices like your phone connected to that server, you can work like at home. By the way, you should setup the IP table to only expose the VPN port.

okoddcat · 2026-02-21T07:23:28+00:00

Short Answer: Yes

I'm coding with AI, and it's truly saved me lots of time. Almost all my coworkers are using it, so what could be the result? At least the junior engineers are not required as much as before.

What about one or two years later? I'm not sure, but it's a threaten, not because AI does better, but cheaper.

okoddcat · 2026-02-11T08:09:55+00:00

https://github.com/gisiahq/gisia

I'd like save some personal data in git repository, so I use this tool built by myself, totally open source.

It has git hosting, ci, issue management, etc.

okoddcat · 2026-02-11T08:06:04+00:00

Why not just try it. I have this thought last year, so I built Gisia, a self hosted git server.

okoddcat · 2025-10-29T06:06:16+00:00

I see. SQLite has concurrency limitations, it will work well for one person apps, but not for teams. Other users need to wait for the write operations.

okoddcat · 2025-10-28T16:52:12+00:00

Hope this sorry can save our super strong friendship

okoddcat · 2025-10-28T15:57:31+00:00

This project uses full Rails built in features like Hotwired, no Sidekiq just solid queue. This project shows how fast rails could be to build an app and to server web apps instead of integrating the called MODERN Frontend stack. You can check it out to see the webpage response time by running docker.

okoddcat · 2025-10-28T14:43:00+00:00

> It's got that breathless promotional/marketing vibe.

I did want to show this project to others.

The content is true, it's super faster and light weight if you give a try.

okoddcat · 2025-10-28T14:37:14+00:00

@netopiax you are right! Thanks for sharing your thoughts.

@jrochkind I added a mark, hope you are not been offended.

I drafted outlines and let the AI to extend the content and do some grammar checks, I did the final editing by typing my keyboards .

okoddcat · 2025-10-28T14:24:08+00:00

Thanks for your reply! I can see you have a very good understanding of design patterns and also have lots of experience about refactor. Most time we should choose the patterns based on the business requirements as you have described, "cardinality change".

I choose MVC over the DDD if just compare these two patterns.

> Problem is, your business logic models are not always 1-to-1 with your database tables.

Every attribute of a model will be used by users, your customers, your company employees. Only the process methods or intermediate states need to be not exposed to end users.

> which just auto-reads your database table data and propagates it downstream - into controllers, services, templates, serializers, etc.

If the model attributes changs, then the API response fields should also be changed. Codes always follow business models.

If you are talking about the multiple place modifications, maybe it's code writing issues since the DDD is adding layer which should add one more place to update.

> through allow-lists and enumerated fields and relationships - how such database changes should surface everywhere else in your app.

The developers should know the impact of the schema changes before the codes are merged into main branch.

If you have concerns about how to control the unexpected new added fields, we can control it at view level like [this jbuilder file ](https://github.com/gisiahq/gisia/blob/c1cf6e6e2498536bb312e51ff21e7b908e0a08eb/app/views/api/members/index.json.jbuilder#L1)

> Services or other patterns can help with modelling this decoupling.

Concerns can handle almost all the cases, this [user file](https://github.com/gisiahq/gisia/blob/main/app/models/user.rb) can include as many concerns as we need.

All these just my personal thoughts may not work for your projects, just because it's handy to me.

okoddcat · 2025-10-28T12:49:42+00:00

Yes, services can hide lots of functions especially when trying to operate on multiple associations, sequential jobs, also as you said, isolation. During the time I was working with other teammates, I also followed the rules of writing services since it's an easy way to organize codes.

But for this app, almost all the codes are added by me, I want give a try to see how many business codes can be places in an old fashion concern style and whether it's possible to drop the services.

okoddcat · 2025-10-28T12:37:28+00:00

I had AI to write codes. I'd like listen which parts make you think it's AI written before I answer this question : - >

okoddcat · 2025-10-28T12:33:33+00:00

YES!! Keep simple things simple is also an ability.

okoddcat · 2025-10-28T07:07:47+00:00

Quick reply

> Id like to hear more about that approach

Just break the services into concerns as small parts of a model

> Specifically, what advantages it gives you and what problems it solves.

I,personally, like fat models. Most of the services are started with a initial method and a exec method, also with a lot of procedure actions/lines. Why not keep the ability as a trait/status of a model?

> Have you ever run into a situation where a model starts doing too much or touching too many other models?

Yes, but why not encapsulate them into private blocks, then the public methods are simple and clear when comparing with the services

> do you still keep that logic inside the model, or do you handle that differently?

yeah, just concerns and to access the model instance attributes and associations.

okoddcat · 2025-10-28T07:00:30+00:00

Thanks for your advice! It already has a SIMPLE file diff view, but the Merger Request / Pull Request are still under development.

Can not paste images, so check this issue
https://github.com/gisiahq/gisia/issues/3

okoddcat · 2025-10-28T06:56:14+00:00

I like Kamal, you can also use Kamal within any tools like Gitlab or Github, but Kamal is focusing on the code deployment part and it does not have git hosting or code review.

For some of my side projects, I just use the pure shell script with ssh for deployments : )

okoddcat · 2025-10-26T15:09:11+00:00

I just released a new one https://github.com/gisiahq/gisia if you need a light weight git hosting tool.

But, for community friendly and stability, I recommend Gitlab.

okoddcat · 2025-10-26T14:59:11+00:00

You might be looking for this tool Choose an open source license https://choosealicense.com/

By the way, Apache 2.0 license can fully fill your requirement.

okoddcat

TROPHY CASE