Fixed local http git repo support

[costa]

What was the end-user or developer problem that led to this PR?

See #9001

What is your fix for the problem, implemented in this PR?

Duplicate the functionality implemented in #7547

Make sure the following tasks are checked

• Describe the problem / feature
• Write tests for features and bug fixes
• Write code to solve the problem
• Make sure you follow the current code style and write meaningful commit messages without tags

p.s. Oh, and also containerised (with docker) test env was added.

[hsbt]

Can you remove Dockerfile and related changes? I don't use that.

If you interest that to use develop RubyGems, please consider to integrate the current devcontainer support of this repository.

[costa]

@hsbt Dear Hiroshi, I'll make just this one attempt to convince you to keep the setup.
I'm using this standard of a simple dockerised bin/test in all my projects, it's dead-simple, explicit and straightforward way to run all the project's tests/specs — in a standard (Docker-based) env — and to have a seal on the code's ultimate correctness, CI/CD or not. I'm open to any suggestions, questions or comments, and I will remove that commit from this PR, of course, to get the rest of the changes merged, if you're unconvinced. Thank you for your work.

[colby-swandale]

I agree with @hsbt that this is not something we're looking to adopt currently.

[costa]

OK, @hsbt, please confirm, and I'll immediately remove these 39 lines from the 200K+(!) LoC project that might help casual contributors (who are definitely not "we") with a single entry point to running all the tests, having a single dependency (the ubiquitous Docker) at that. No problem.

[hsbt]

Please remove them at first.

[costa]

Please remove them at first.

@hsbt done

[costa]

@hsbt LGTM

[costa]

ping

[costa]

@hsbt Yes, and? Please?

[hsbt]

In my understanding with #7547, Why would you want to git clone and use it via a local http server without using the path: option?

[costa]

@hsbt

In my understanding with #7547, Why would you want to git clone and use it via a local http server without using the path: option?

This PR fixes a bug with rubygems functionality which I believe should support everything git supports.

Now, serving git repos with dumb HTTP servers (read-only) is useful in many low-profile scenarios.

In my "self server" (docker-host-based) case, illustrated here: https://medium.com/@costa/git-decentralized-a25f00fd2955 -- when I serve git repos via dumb HTTP, this uses simple p2p sharing stack -- and enables p2p git-based communication, as well as makes container builds straightforward.

[costa]

@hsbt Hi, how're you doing? Now, this PR is one of the oldest open ones. I've just updated its branch. How can I help you with accepting or rejecting it? Thank you.