Forgejo is looking for input from #Forgejo administrators....

Forgejo is looking for input from #Forgejo administrators.

We are considering dropping support for using Microsoft SQL Server as a database that can be used with Forgejo. We would love to hear your input, especially those using it (if there are any 👀), on this matter. See our rationale and current discussion at https://codeberg.org/forgejo/discussions/issues/122, we're looking forward to your input on this matter.

Like 3 April at 14:12 | Open on floss.social

15 comments

networkException

@forgejo yes please, burn it

3 April at 14:13 | Open on chaos.social

Christian

@forgejo

3 April at 14:14 | Open on chaos.social

TheTomas

@forgejo Microsoft? Who's that?

3 April at 14:18 | Open on social.toot9.de

Jing Luo

@forgejo and dropping it will bring forgejo one step closer to be accepted into debian's main repo (currently forgejo does not satisfy dfsg)

3 April at 14:19 | Open on mastodon.jing.lgbt

Gusted

@jing @forgejo Oh that's interesting to know, is there a page that lists these requirements? Or is there an already existing issue for Forgejo's inclusion?

3 April at 14:28 | Open on social.linux.pizza

Risotto

@jing @forgejo wait... Where does having a client to a proprietary DB violate dfsg?

https://www.debian.org/social_contract

3 April at 14:31 | Open on tech.lgbt

Vortec Space

@forgejo I'm not on Forgejo yet but I intend to move my one-person Gitea instance next time I update. Go for it, I'm just using SQLite. Can't believe Windows servers are even real these days.