From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
I'll try that :) Do you have any hint on how to "start debugging"? Maybe just some search engine for "debug fcgiwrap"? Thanks again, I'll post here when I find a solution. -- Gabriel Augendre
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
Sadly nothing useful, at least I guess tail -f /var/log/nginx/* ==> nginx/access.log <== 192.168.0.10 - - [21/Nov/2020:15:16:44 +0100] "GET /~crocmagnon/test/info/refs?service=git-upload-pack HTTP/1.0" 403 15 "-" "git/2.29.2" "[some ipv6 address]" -- Gabriel Augendre
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
Thanks, Here's what I have: -rw-r--r-- 1 git git 4.4K Nov 20 21:22 git.sr.ht.log -rw-r--r-- 1 git git 13.7K Nov 21 08:29 gitsrht-dispatch -rw-r--r-- 1 git git 23.5K Nov 21 08:29 gitsrht-keys -rw-r--r-- 1 git git 4.9K Nov 21 08:29 gitsrht-shell -rw-r--r-- 1 git git 648 Nov 20 21:07 gitsrht-update-hook I did a `tail -f git*` and tried to `git clone` with https but nothing moved. -- Gabriel Augendre
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
Yeah I noticed some issues when cloning with ssh indeed, I created and chowned the ones that were mentioned in stderr. Could you please list all the files that should exist? Maybe I’m missing some? -- Gabriel Augendre Sent from a mobile device / Envoyé depuis un appareil mobile
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
A few things I forgot to mention: * The repo is public * I have another nginx to handle all my incoming http(s) traffic before git.sr.ht's. Here's the config: https://paste.sr.ht/~crocmagnon/b403d67a5c716d74bf3cd00e301ca329d81961ca In this config, http://192.168.0.56:80 is the git.sr.ht host. -- Gabriel Augendre
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
Hello, I just spent a couple of hours setting up a self-hosted instance of git.sr.ht. First, a quick note: it was impossible to use ssh to pull/push to git repos unless I added a password to the `git` user on a fresh alpine install. Maybe this should be documented? I can send a patch if needed. Now onto my issue: I can't clone using https. Here's the log from the git clone command: $ git clone https://git.srht.augendre.info/~crocmagnon/test
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
I’ve often seen and used the minus sign to reverse
search order, like so:
sort:comments
sort:-comments
But I don’t know what sourcehut currently uses for
its own ordering.
--
Gabriel Augendre
Sent from a mobile device
/ Envoyé depuis un appareil mobile
> Le 28 août 2020 à 07:36, Enterprisey <apersonwiki@gmail.com> a écrit :
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
> This seems like a lot of work for not too much benefit. That's right! > I suppose that depends on your definition of integrated. Personally, > my definition is "a CI provider offers one-click integration". I suppose so, sorry for not having clarified that from the beginning. Your definition makes sense, mine was more like "one platform to rule them all". > For quite some time that wasn't necessarily true on Github either, and when you could, it required multiple configured services anyway.
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
> The sticking point here is CI for proprietary OSes, it's not about > mailing lists or bugtrackers or source code. > > Drew DeVault has made the reasonable statement that he doesn't feel like > adding proprietary OS support for builds.sr.ht only -- he never said > anything about making these people unwelcome, merely that he won't > support running his infrastructure (in this case the build workers) on > such OSes. People are still free to talk about them, store source code > intended to run on them, etc... I think you're making a very good point, however you may have missed mine, which was more about the /integration/. Let's say I, as a macOS software maintainer, want an integrated environment for everything I listed before (source code, CI, bug trackers, etc.). I currently can't have that on sourcehut and after Drew's answer I feel safe to say that
From Gabriel Augendre to ~sircmpwn/sr.ht-discuss
> I have no intention of supporting proprietary operating systems on > builds.sr.ht at any time. Ok, at least that's very clear. Thanks for the heads up. Would you accept a patch to the docs stating that? Or maybe it's already written somewhere and I missed it? Genuinely trying to understand: Sadly not all free and open source software runs on free and open source systems. Does that mean that FOSS maintainers that want/need to support proprietary OS and want an integrated environment for their source code, CI builds, mailing lists and bug trackers are not welcome on sourcehut?