The Discourse instance is located behind the GFW, thus we use a SOCKS5 proxy for Git. We have a couple of plugins installed, so either rebuilding or bootstrapping the app clones all of these repos over and over again. Unfortunately the cloning results in timeout regularly, so the whole process start…

[이미지] leoniscsem: If I could only run the launcher with a flag that says something like “ OK dude, code is here, no need to clone… just bootstrap for now ”, :grinning: That’s what your own caching proxy would do (or so I’d think). I’d check out squid . Then you’d see that launcher pulled from …

I’m not expert in these mattters, but I think that the solution is a caching proxy for the stuff that you’re downloading. There is a web.china.template.yml, are you using that?

[이미지] pfaffman: There is a web.china.template.yml , are you using that? Of course. I use the Chinese Ruby source in all Rails applications, glad to have that at least. What puzzles me: All the repos (including those of the plugins) are now already cloned, just this yarn subprocess invokes the…

Yes, we have some experience with Squid to some certain extent. This needs a general solution anyway, as I can’t spend hours with a manual Discourse upgrade every time. For a few months using a regular socks5 proxy had worked out, yet it’s a constant game of whack-a-mole with the GFW and accessing G…

[이미지] leoniscsem: just this yarn subprocess invokes the following: INFO -- : > cd /var/www/discourse && [ ! -d 'node_modules' ] || su discourse -c 'yarn install --production && yarn cache clean' For whatever reason the GFW doesn’t like too many git clone processes after another, That should…

Oh, directly after that followed some subprocess that cloned something and failed. Unfortunately I can’t reproduce the error log now. It had pulled something from GitHub definitely, as the error message was thge same TLS handshake error / timeout. It’s not important now though. Usually npm for whate…

Maybe it was package.json main "typescript": "^5.9.3" }, "scripts": { "dev": "bin/dev", "lint": "concurrently \"pnpm:lint:*(!fix)\" --names \"lint:\"", "lint:fix": "concurrently \"pnpm:lint:*:fix\" --nam…

[이미지] Falco: "moment-timezone-names-translations": "https://github.com/discourse/moment-timezone-names-translations", You are the man! Exactly that broke my upgrade.

That is pretty darn stable, any chance we can push it to the NPM registry now @pmusaraj ?

Oh yes, definitely, let’s do that.

모든 것을 다시 복제하지 않고 부트스트랩/재빌드할 수 있나요?

지원

Falco (Falco) 1월 10, 2022, 5:55오후 10

꽤 안정적으로 보이는데, 지금 NPM 레지스트리에 올릴 수 있을까요? @pmusaraj

글		댓글	조회수
Upgrade from within China fails due to git issues Self-hosting	18	4263	7월 12, 2023
Proxy during discourse bootstrap Self-hosting	2	1629	6월 1, 2018
Install Discourse on an isolated CentOS 7 server Sysadmins how-to , install	23	11805	7월 5, 2022
Can't install reaction plugin Self-hosting reactions	20	1089	6월 11, 2024
Continuous Issues when Rebuilding Discourse Self-hosting	5	777	3월 19, 2024

모든 것을 다시 복제하지 않고 부트스트랩/재빌드할 수 있나요?

Related topics