Gitlab is overbloated shit garbage

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

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

til that firefox renders invalid feed xml, thanks mozilla

should be fixed now

where? i’m not seeing anything while logged out

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

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: Hide email addresses everywhere · Issue #3358 · gogs/gogs · GitHub

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&lt;/link&gt;, etc.

sure, why not. should be fixed now.

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

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

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!

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.

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?

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

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)

forgot about docker --restart=always