Git repositories move to https://tt-rss.org

[fox]

>Also, with respect to your fix: assuming mod_rewrite is installed and enabled is bad form.

there's also the whole nginx thing and the fact that our public repositories are mapped under /.git/ and eughhhhh

[ahaha]

The installation guide on your wiki still shows "https://tt-rss.org/git/tt-rss.git tt-rss" as the tt-rss repository. Please update with the new address "https://tt-rss.org/gitlab/fox/tt-rss.git"

[fox]

an excellent first post

made me ahaha

[sleeper_service]

such amazing humor!

[JustAMacUser]

@fox,

Just wondering if you're planning to open your GitLab install to allow others to fork the repository? My account tells me I cannot because my project limit is 0.

Obviously I can submit patches without this, but I like the convenience, etc. of having it all in the same place.

[fox]

if you are a project member you can make branches which i think is an acceptable compromise.

[nameless]

gitlab 8.0 has been published
https://about.gitlab.com/2015/09/22/git ... -released/

[fox]

later, when im sober

[Tehlanie]

It has been a LONG time since I upgraded tt-rss (I was originally using the Github.com branhc), and went to upgrade it today. Performed the steps in the first post. Then went to do a pull however I received an error:

server:/var/www/tt-rss$ sudo git pull origin master
fatal: unable to access 'https://tt-rss.org/git/tt-rss.git/': Failed to connect to tt-rss.org port 443: Connection timed out

I assume that git is up and running?

EDIT:
I also attempted to use the url found on this page: https://tt-rss.org/gitlab/fox/tt-rss which states: https://tt-rss.org/gitlab/fox/tt-rss.git

This also received a time out

[JustAMacUser]

I'm using:

Code: Select all

https://tt-rss.org/gitlab/fox/tt-rss.git

And it seems to be working. It's possible it was just a glitch in the route (dropped packet, etc.).

Have you tried running a trace route from the server on which TT-RSS runs to this site?

What is the output of the following command:

Code: Select all

git remote -v

[Tehlanie]

I'm using:

Code: Select all

https://tt-rss.org/gitlab/fox/tt-rss.git

And it seems to be working. It's possible it was just a glitch in the route (dropped packet, etc.).

Have you tried running a trace route from the server on which TT-RSS runs to this site?

What is the output of the following command:

Code: Select all

git remote -v

Just cleared it out and followed op's instructions again, so:
server:/var/www/tt-rss$ sudo git remote -v
origin https://tt-rss.org/git/tt-rss.git (fetch)
origin https://tt-rss.org/git/tt-rss.git (push)

traceroute seems to time out from multiple machines along the path to tt-rss.org so that could be a potential issue. It eventually gets there though:
From Machine 1)
Tracing route to tt-rss.org [94.247.246.182]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 1 ms <1 ms A [10.0.1.1]
3 10 ms 11 ms 11 ms 96.120.89.137
4 12 ms 13 ms 11 ms te-0-7-0-1-sur04.sfmission.ca.sfba.comcast.net [68.85.103.141]
5 13 ms 18 ms 13 ms be-310-ar01.hayward.ca.sfba.comcast.net [162.151.79.81]
6 * * 14 ms lag-14.ear2.SanJose1.Level3.net [4.68.72.101]
7 * * * Request timed out.
8 161 ms 161 ms 161 ms OJSC-ROSTEL.ear2.Frankfurt1.Level3.net [62.67.36.230]
9 189 ms 197 ms 191 ms 95.167.93.77
10 197 ms 204 ms 196 ms 188.254.104.106
11 201 ms 203 ms 196 ms 109-167-195-126.westcall.net [109.167.195.126]
12 201 ms 199 ms 200 ms 109-167-195-149.westcall.net [109.167.195.149]
13 203 ms 205 ms 203 ms 94-247-241-130.westcall.net [94.247.241.130]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 199 ms 196 ms 198 ms ppp.volgo-balt.ru [94.247.246.182]

Machine 2 (TT-RSS machine)
server:/var/www/tt-rss$ traceroute tt-rss.org
traceroute to tt-rss.org (94.247.246.182), 30 hops max, 60 byte packets
1 10.10.10.1 (10.10.10.1) 0.254 ms 1.155 ms 1.154 ms
2 * * *
3 dtr01kllrtx-tge-0-1-1-1.kllr.tx.charter.com (96.34.112.145) 17.238 ms 18.298 ms 18.401 ms
4 crr01nrictx-bue-3.nric.tx.charter.com (96.34.112.180) 18.470 ms 19.102 ms 19.133 ms
5 crr01ftwotx-bue-4.ftwo.tx.charter.com (96.34.113.116) 22.972 ms 23.116 ms 23.055 ms
6 bbr01dllstx-bue-2.dlls.tx.charter.com (96.34.2.32) 21.875 ms 18.424 ms 19.290 ms
7 bbr01blvlil-bue-805.blvl.il.charter.com (96.34.0.16) 52.297 ms 51.348 ms 52.316 ms
8 bbr01ashbva-tge-0-0-0-8.ashb.va.charter.com (96.34.0.244) 79.721 ms 80.707 ms 80.798 ms
9 prr01ashbva-bue-6.ashb.va.charter.com (96.34.3.89) 74.061 ms 75.068 ms 75.144 ms
10 ahn.eqx.transtelecom.net (206.126.236.233) 75.184 ms 75.359 ms 72.163 ms
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Even MTR can't get past hop 11. Seems like routing issues are going on somewhere around the East Coast US and EU.

[sleeper_service]

Even MTR can't get past hop 11. Seems like routing issues are going on somewhere around the East Coast US and EU.

yet, you're able to post.

[fox]

well his tt-rss and the machine he's posting from could be on different ISPs

in any case this kinda thing usually gets fixed fast, which is good because there's not much you can do about it (other than using a proxy, i guess)

[Tehlanie]

I am still unable to connect to the server. It times out.

[Tehlanie]

After waiting this long for it to not be fixed - I forked it to Github (FWIW, the fork is private) so I could pull it down and update.

However, I noticed, that it only forked it up to the end of August. Any reason for that?
I am on version Tiny Tiny RSS v15.7 (3ad4589) after the pull.