14

Hi,

Just tried using the new remote URL as above:

admin@gently-jessie:~/rss.gently.org.uk/public/htdocs$ git remote set-url origin git@git.tt-rss.org:git/tt-rss.git
admin@gently-jessie:~/rss.gently.org.uk/public/htdocs$ git fetch
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

What’s the correct URL?

Andy

15

i’m working on redirects for previous https clone urls

nginx shakes fist

16

Ah ok. Neither git or https URLs are working for me at the moment.

I’ll wait for things to stabilise :slight_smile:

Andy

17

for SSH clone urls the easiest way is doing something like that

git remote get-url origin | sed s/:fox/:git/ | xargs git remote set-url origin

#!/bin/sh

for i in *; do
	if [ -d "$i" ]; then
		cd $i
		URL=$(git remote get-url origin 2>/dev/null)

		case "$URL" in
			*git.tt-rss.org:fox* )
				URL=$(echo $URL | sed s/:fox/:git/)

				git remote set-url origin "$URL"
			;;
		esac

		cd ..
	fi
done

yeah redirects are a pain (only got them partially working so far), native gogs urls work fine tho

i.e. git@git.tt-rss.org:git/tt-rss.git and https://git.tt-rss.org/git/tt-rss.git

UPDATE

https clone urls which look like this: tt-rss.git - should work now:

working on a few other variants

UPDATE

all other variants i could remember should work now

i.e. /fox/tt-rss.git ; /gitlab/fox/tt-rss.git

note that gogs doesn’t seem to have RSS feeds for everything, too bad i guess

e: tfw you shutdown gitlab and VM suddenly has 3/4 RAM free

18

For people that might wonder how to update to the new repository, this is what worked for me:

git remote rm origin
git remote add origin https://git.tt-rss.org/git/tt-rss
git branch --set-upstream-to=origin/master master
git up

Nothing earth shattering if you know how to use git… The last command is an alias for "!git remote update -p; git merge --ff-only @{u}" which I find useful.

19

Tiny Tiny RSS – Feeds added some barebones rss feeds for repository activity (master branch)

20

https://tt-rss.org/feeds/tt-rss.xml

LibXML error 76 at line 307 (column 11): Opening and ending tag mismatch: rss line 1 and channel

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

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