Gitlab is overbloated shit garbage


#21

ehm, feeds don’t parse using https://fakecake.org/myfeedsucks/


#22

Somewhat annoying that Gogs exposes e-mail addresses @ https://git.tt-rss.org/explore/users .


#23

til that firefox renders invalid feed xml, thanks mozilla

should be fixed now


#24

where? i’m not seeing anything while logged out


#25

When you’re logged in you can view every user’s address. Guess they figure collaboration or something.


#26

well unless you used a dummy your email is going to be in the commit list regardless, otherwise just use throwaways or something. i haven’t enabled any email verification when registering.

also: https://github.com/gogits/gogs/issues/3358


#27

Would you be up for linking to each commit? The item for “update contributing.md” would have <link>https://git.tt-rss.org/git/tt-rss/commit/890a7be0c63af9ca8bc36b521fda0a8e043906f6</link>, etc.


#28

sure, why not. should be fixed now.


#29

Does this replace the previous way to update TT-RSS using Git?


#30

except for the repository URL nothing changed

also, i’ve added support for most previous URLs so most likely you don’t need to do anything at all


#31

Nope. This is just what I did to make it work for me. Thought it might be useful for others so added it here.

There is nothing official (aka Fox approved) about these commands!


#32

OK, I’m arriving here because my feed for git activity didn’t work. I found the new bare feeds for that, many thanks.

I’m just mentionning Gitea. This is a Gogs fork, because people couldn’t wait for some requests to be merged. I found it a bit more usable, but honestly, I really don’t mind if you stick to Gogs. I just wanted to mention it.

And yes, Gitlab, despite its very nice UI, is a hardware killer.


#33

Came here to bitch about the irony of moving tt-rss to a new Git hosting platform that doesn’t provide RSS feeds, but found that it was (sort of) already covered.

Regarding migration of end-user clones: Can’t you just edit the .git/config file to point the origin remote at a new URL?


#34

I had to add “git pull” between the second and third command else it complained about the requested upstream branch not existing.


#35

Currently getting “502 Bad Gateway” for all of git.tt-rss.org even in the browser. If there’s an issue there’s an issue, but I just wanted to make sure it wasn’t my end and/or any server protection kicking in (I probably hit the server at most 1-2x/day, but you never know)


#36

forgot about docker --restart=always